opendev/elastic-recheck
Code Issues Proposed changes

Clarifies documentation about wildcards in queries

Browse Source 
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
This commit is contained in:
Anita Kuno 2014-06-25 12:08:08 -04:00
parent f35a7a96bb
commit 2f39f8afa1
1 changed files with 4 additions and 4 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

8
README.rst
View File

@ -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.:
::