simple-query-string-query.asciidoc 4.3 KB

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596979899100101102103104105106107108109110111112113114115116117118119120121122
  1. [[query-dsl-simple-query-string-query]]
  2. === Simple Query String Query
  3. A query that uses the SimpleQueryParser to parse its context. Unlike the
  4. regular `query_string` query, the `simple_query_string` query will never
  5. throw an exception, and discards invalid parts of the query. Here is
  6. an example:
  7. [source,js]
  8. --------------------------------------------------
  9. {
  10. "simple_query_string" : {
  11. "query": "\"fried eggs\" +(eggplant | potato) -frittata",
  12. "analyzer": "snowball",
  13. "fields": ["body^5","_all"],
  14. "default_operator": "and"
  15. }
  16. }
  17. --------------------------------------------------
  18. The `simple_query_string` top level parameters include:
  19. [cols="<,<",options="header",]
  20. |=======================================================================
  21. |Parameter |Description
  22. |`query` |The actual query to be parsed. See below for syntax.
  23. |`fields` |The fields to perform the parsed query against. Defaults to the
  24. `index.query.default_field` index settings, which in turn defaults to `_all`.
  25. |`default_operator` |The default operator used if no explicit operator
  26. is specified. For example, with a default operator of `OR`, the query
  27. `capital of Hungary` is translated to `capital OR of OR Hungary`, and
  28. with default operator of `AND`, the same query is translated to
  29. `capital AND of AND Hungary`. The default value is `OR`.
  30. |`analyzer` |The analyzer used to analyze each term of the query when
  31. creating composite queries.
  32. |`flags` |Flags specifying which features of the `simple_query_string` to
  33. enable. Defaults to `ALL`.
  34. |`lowercase_expanded_terms` | Whether terms of prefix and fuzzy queries should
  35. be automatically lower-cased or not (since they are not analyzed). Defaults to
  36. `true`.
  37. |`analyze_wildcard` | Whether terms of prefix queries should be automatically
  38. analyzed or not. If `true` a best effort will be made to analyze the prefix. However,
  39. some analyzers will be not able to provide a meaningful results
  40. based just on the prefix of a term. Defaults to `false`.
  41. |`locale` | Locale that should be used for string conversions.
  42. Defaults to `ROOT`.
  43. |`lenient` | If set to `true` will cause format based failures
  44. (like providing text to a numeric field) to be ignored.
  45. |`minimum_should_match` | The minimum number of clauses that must match for a
  46. document to be returned. See the
  47. <<query-dsl-minimum-should-match,`minimum_should_match`>> documentation for the
  48. full list of options.
  49. |=======================================================================
  50. [float]
  51. ===== Simple Query String Syntax
  52. The `simple_query_string` supports the following special characters:
  53. * `+` signifies AND operation
  54. * `|` signifies OR operation
  55. * `-` negates a single token
  56. * `"` wraps a number of tokens to signify a phrase for searching
  57. * `*` at the end of a term signifies a prefix query
  58. * `(` and `)` signify precedence
  59. * `~N` after a word signifies edit distance (fuzziness)
  60. * `~N` after a phrase signifies slop amount
  61. In order to search for any of these special characters, they will need to
  62. be escaped with `\`.
  63. [float]
  64. ==== Default Field
  65. When not explicitly specifying the field to search on in the query
  66. string syntax, the `index.query.default_field` will be used to derive
  67. which field to search on. It defaults to `_all` field.
  68. So, if `_all` field is disabled, it might make sense to change it to set
  69. a different default field.
  70. [float]
  71. ==== Multi Field
  72. The fields parameter can also include pattern based field names,
  73. allowing to automatically expand to the relevant fields (dynamically
  74. introduced fields included). For example:
  75. [source,js]
  76. --------------------------------------------------
  77. {
  78. "simple_query_string" : {
  79. "fields" : ["content", "name.*^5"],
  80. "query" : "foo bar baz"
  81. }
  82. }
  83. --------------------------------------------------
  84. [float]
  85. ==== Flags
  86. `simple_query_string` support multiple flags to specify which parsing features
  87. should be enabled. It is specified as a `|`-delimited string with the
  88. `flags` parameter:
  89. [source,js]
  90. --------------------------------------------------
  91. {
  92. "simple_query_string" : {
  93. "query" : "foo | bar + baz*",
  94. "flags" : "OR|AND|PREFIX"
  95. }
  96. }
  97. --------------------------------------------------
  98. The available flags are: `ALL`, `NONE`, `AND`, `OR`, `NOT`, `PREFIX`, `PHRASE`,
  99. `PRECEDENCE`, `ESCAPE`, `WHITESPACE`, `FUZZY`, `NEAR`, and `SLOP`.