mirror of
https://github.com/honeymoose/OpenSearch.git
synced 2025-04-09 16:58:33 +00:00
1cfb6a79f1
* Cut the `has_child` and `has_parent` queries over to use Lucene's query time global ordinal join. The main benefit of this change is that parent/child queries can now efficiently execute if parent/child queries are wrapped in a bigger boolean query. If the rest of the query only hit a few documents both has_child and has_parent queries don't need to evaluate all parent or child documents any more. * Cut the `_parent` field over to use doc values. This significantly reduces the on heap memory footprint of parent/child, because the parent id values are never loaded into memory. Breaking changes: * The `type` option on the `_parent` field can only point to a parent type that doesn't exist yet, so this means that an existing type/mapping can't become a parent type any longer. * The `has_child` and `has_parent` queries can no longer be use in alias filters. All these changes, improvements and breaks in compatibility only apply for indices created with ES version 2.0 or higher. For indices creates with ES <= 2.0 the older implementation is used. It is highly recommended to re-index all your indices with parent and child documents to benefit from all the improvements that come with this refactoring. The easiest way to achieve this is by using the scan and bulk apis using a simple script. Closes #6107 Closes #8134
75 lines
1.9 KiB
Plaintext
75 lines
1.9 KiB
Plaintext
[[query-dsl-has-child-query]]
|
|
== Has Child Query
|
|
|
|
The `has_child` filter accepts a query and the child type to run against, and
|
|
results in parent documents that have child docs matching the query. Here is
|
|
an example:
|
|
|
|
[source,js]
|
|
--------------------------------------------------
|
|
{
|
|
"has_child" : {
|
|
"type" : "blog_tag",
|
|
"query" : {
|
|
"term" : {
|
|
"tag" : "something"
|
|
}
|
|
}
|
|
}
|
|
}
|
|
--------------------------------------------------
|
|
|
|
[float]
|
|
=== Scoring capabilities
|
|
|
|
The `has_child` also has scoring support. The
|
|
supported score types are `min`, `max`, `sum`, `avg` or `none`. The default is
|
|
`none` and yields the same behaviour as in previous versions. If the
|
|
score type is set to another value than `none`, the scores of all the
|
|
matching child documents are aggregated into the associated parent
|
|
documents. The score type can be specified with the `score_mode` field
|
|
inside the `has_child` query:
|
|
|
|
[source,js]
|
|
--------------------------------------------------
|
|
{
|
|
"has_child" : {
|
|
"type" : "blog_tag",
|
|
"score_mode" : "sum",
|
|
"query" : {
|
|
"term" : {
|
|
"tag" : "something"
|
|
}
|
|
}
|
|
}
|
|
}
|
|
--------------------------------------------------
|
|
|
|
[float]
|
|
=== Min/Max Children
|
|
|
|
The `has_child` query allows you to specify that a minimum and/or maximum
|
|
number of children are required to match for the parent doc to be considered
|
|
a match:
|
|
|
|
[source,js]
|
|
--------------------------------------------------
|
|
{
|
|
"has_child" : {
|
|
"type" : "blog_tag",
|
|
"score_mode" : "sum",
|
|
"min_children": 2, <1>
|
|
"max_children": 10, <1>
|
|
"query" : {
|
|
"term" : {
|
|
"tag" : "something"
|
|
}
|
|
}
|
|
}
|
|
}
|
|
--------------------------------------------------
|
|
<1> Both `min_children` and `max_children` are optional.
|
|
|
|
The `min_children` and `max_children` parameters can be combined with
|
|
the `score_mode` parameter.
|