mirror of
https://github.com/elastic/kibana.git
synced 2025-04-24 01:38:56 -04:00
Fixes #13563 Brings additional attention to the fact that Kuery uses implicit ANDs whereas Lucene query syntax uses implicit ORs, which could confuse users if they're not aware of the difference.
This commit is contained in:
parent
ea983c3c59
commit
9350243dc0
1 changed files with 2 additions and 1 deletions
|
@ -17,7 +17,8 @@ Multiple search terms are separated by whitespace.
|
|||
|
||||
`response:200 extension:php` will match documents where response matches 200 and extension matches php.
|
||||
|
||||
All terms must match by default. The language supports boolean logic with and/or operators. The above query is equivalent to `response:200 and extension:php`.
|
||||
*All terms must match by default*. The language supports boolean logic with and/or operators. The above query is equivalent to `response:200 and extension:php`.
|
||||
This is a departure from the Lucene query syntax where all terms are optional by default.
|
||||
|
||||
We can make terms optional by using `or`.
|
||||
|
||||
|
|
Loading…
Add table
Add a link
Reference in a new issue