mirror of
https://github.com/honeymoose/OpenSearch.git
synced 2025-02-06 04:58:50 +00:00
dac720d7a1
Add a new cluster setting `search.allow_expensive_queries` which by default is `true`. If set to `false`, certain queries that have usually slow performance cannot be executed and an error message is returned. - Queries that need to do linear scans to identify matches: - Script queries - Queries that have a high up-front cost: - Fuzzy queries - Regexp queries - Prefix queries (without index_prefixes enabled - Wildcard queries - Range queries on text and keyword fields - Joining queries - HasParent queries - HasChild queries - ParentId queries - Nested queries - Queries on deprecated 6.x geo shapes (using PrefixTree implementation) - Queries that may have a high per-document cost: - Script score queries - Percolate queries Closes: #29050 (cherry picked from commit a8b39ed842c7770bd9275958c9f747502fd9a3ea)
76 lines
2.7 KiB
Plaintext
76 lines
2.7 KiB
Plaintext
[[query-dsl]]
|
|
= Query DSL
|
|
|
|
[partintro]
|
|
--
|
|
|
|
Elasticsearch provides a full Query DSL (Domain Specific Language) based on JSON to define queries.
|
|
Think of the Query DSL as an AST (Abstract Syntax Tree) of queries, consisting of two types of
|
|
clauses:
|
|
|
|
Leaf query clauses::
|
|
|
|
Leaf query clauses look for a particular value in a particular field, such as the
|
|
<<query-dsl-match-query,`match`>>, <<query-dsl-term-query,`term`>> or
|
|
<<query-dsl-range-query,`range`>> queries. These queries can be used
|
|
by themselves.
|
|
|
|
Compound query clauses::
|
|
|
|
Compound query clauses wrap other leaf *or* compound queries and are used to combine
|
|
multiple queries in a logical fashion (such as the
|
|
<<query-dsl-bool-query,`bool`>> or <<query-dsl-dis-max-query,`dis_max`>> query),
|
|
or to alter their behaviour (such as the
|
|
<<query-dsl-constant-score-query,`constant_score`>> query).
|
|
|
|
Query clauses behave differently depending on whether they are used in
|
|
<<query-filter-context,query context or filter context>>.
|
|
|
|
[[query-dsl-allow-expensive-queries]]
|
|
Allow expensive queries::
|
|
Certain types of queries will generally execute slowly due to the way they are implemented, which can affect
|
|
the stability of the cluster. Those queries can be categorised as follows:
|
|
* Queries that need to do linear scans to identify matches:
|
|
** <<query-dsl-script-query, `script queries`>>
|
|
* Queries that have a high up-front cost:
|
|
** <<query-dsl-fuzzy-query,`fuzzy queries`>>
|
|
** <<query-dsl-regexp-query,`regexp queries`>>
|
|
** <<query-dsl-prefix-query,`prefix queries`>> without <<index-prefixes, `index_prefixes`>>
|
|
** <<query-dsl-wildcard-query, `wildcard queries`>>
|
|
** <<query-dsl-range-query, `range queries>> on <<text, `text`>> and <<keyword, `keyword`>> fields
|
|
* <<joining-queries, `Joining queries`>>
|
|
* Queries on <<prefix-trees, deprecated geo shapes>>
|
|
* Queries that may have a high per-document cost:
|
|
** <<query-dsl-script-score-query, `script score queries`>>
|
|
** <<query-dsl-percolate-query, `percolate queries`>>
|
|
|
|
The execution of such queries can be prevented by setting the value of the `search.allow_expensive_queries`
|
|
setting to `false` (defaults to `true`).
|
|
--
|
|
|
|
include::query-dsl/query_filter_context.asciidoc[]
|
|
|
|
include::query-dsl/compound-queries.asciidoc[]
|
|
|
|
include::query-dsl/full-text-queries.asciidoc[]
|
|
|
|
include::query-dsl/geo-queries.asciidoc[]
|
|
|
|
include::query-dsl/shape-queries.asciidoc[]
|
|
|
|
include::query-dsl/joining-queries.asciidoc[]
|
|
|
|
include::query-dsl/match-all-query.asciidoc[]
|
|
|
|
include::query-dsl/span-queries.asciidoc[]
|
|
|
|
include::query-dsl/special-queries.asciidoc[]
|
|
|
|
include::query-dsl/term-level-queries.asciidoc[]
|
|
|
|
include::query-dsl/minimum-should-match.asciidoc[]
|
|
|
|
include::query-dsl/multi-term-rewrite.asciidoc[]
|
|
|
|
include::query-dsl/regexp-syntax.asciidoc[]
|