From 2f39f8afa1798c8c5735e17bfedac5023a765a16 Mon Sep 17 00:00:00 2001 From: Anita Kuno Date: Wed, 25 Jun 2014 12:08:08 -0400 Subject: [PATCH] Clarifies documentation about wildcards in queries Currently the document reads as though wildcards are permissible in certain situations. If wildcards are used in a query, the query is likely to be rejected on that basis. This patch clarifies that wildcards are not to be used in elastic search queries. Change-Id: Ica400397f21963e78ae71c0efcc6bfdc2653ae53 --- README.rst | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/README.rst b/README.rst index b2526041..f94d2a4f 100644 --- a/README.rst +++ b/README.rst @@ -51,10 +51,10 @@ Guidelines for good queries: tempest and devstack logs. - Avoid the use of wildcards in queries since they can put an undue burden on - the query engine. A common case where wildcards would be useful are in - querying against a specific set of build_name fields, e.g. gate-nova-python26 - and gate-nova-python27. Rather than use build_name:gate-nova-python*, list - the jobs with an OR, e.g.: + the query engine. A common case where wildcards are used and shouldn't be are + in querying against a specific set of build_name fields, + e.g. gate-nova-python26 and gate-nova-python27. + Rather than use build_name:gate-nova-python*, list the jobs with an OR, e.g.: ::