simple-query-string-query.asciidoc 4.7 KB

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