mirror of
https://github.com/honeymoose/OpenSearch.git
synced 2025-02-05 20:48:22 +00:00
25aac4f77f
The "include_type_name" parameter was temporarily introduced in #37285 to facilitate moving the default parameter setting to "false" in many places in the documentation code snippets. Most of the places can simply be reverted without causing errors. In this change I looked for asciidoc files that contained the "include_type_name=true" addition when creating new indices but didn't look likey they made use of the "_doc" type for mappings. This is mostly the case e.g. in the analysis docs where index creating often only contains settings. I manually corrected the use of types in some places where the docs still used an explicit type name and not the dummy "_doc" type.
76 lines
2.1 KiB
Plaintext
76 lines
2.1 KiB
Plaintext
[[search-aggregations-bucket-nested-aggregation]]
|
|
=== Nested Aggregation
|
|
|
|
A special single bucket aggregation that enables aggregating nested documents.
|
|
|
|
For example, lets say we have an index of products, and each product holds the list of resellers - each having its own
|
|
price for the product. The mapping could look like:
|
|
|
|
[source,js]
|
|
--------------------------------------------------
|
|
PUT /index
|
|
{
|
|
"mappings": {
|
|
"properties" : {
|
|
"resellers" : { <1>
|
|
"type" : "nested",
|
|
"properties" : {
|
|
"name" : { "type" : "text" },
|
|
"price" : { "type" : "double" }
|
|
}
|
|
}
|
|
}
|
|
}
|
|
}
|
|
--------------------------------------------------
|
|
// CONSOLE
|
|
// TESTSETUP
|
|
<1> The `resellers` is an array that holds nested documents under the `product` object.
|
|
|
|
The following aggregations will return the minimum price products can be purchased in:
|
|
|
|
[source,js]
|
|
--------------------------------------------------
|
|
GET /_search
|
|
{
|
|
"query" : {
|
|
"match" : { "name" : "led tv" }
|
|
},
|
|
"aggs" : {
|
|
"resellers" : {
|
|
"nested" : {
|
|
"path" : "resellers"
|
|
},
|
|
"aggs" : {
|
|
"min_price" : { "min" : { "field" : "resellers.price" } }
|
|
}
|
|
}
|
|
}
|
|
}
|
|
--------------------------------------------------
|
|
// CONSOLE
|
|
// TEST[s/GET \/_search/GET \/_search\?filter_path=aggregations/]
|
|
// TEST[s/^/PUT index\/_doc\/0\?refresh\n{"name":"led", "resellers": [{"name": "foo", "price": 350.00}, {"name": "bar", "price": 500.00}]}\n/]
|
|
|
|
As you can see above, the nested aggregation requires the `path` of the nested documents within the top level documents.
|
|
Then one can define any type of aggregation over these nested documents.
|
|
|
|
Response:
|
|
|
|
[source,js]
|
|
--------------------------------------------------
|
|
{
|
|
...
|
|
"aggregations": {
|
|
"resellers": {
|
|
"doc_count": 0,
|
|
"min_price": {
|
|
"value": 350
|
|
}
|
|
}
|
|
}
|
|
}
|
|
--------------------------------------------------
|
|
// TESTRESPONSE[s/\.\.\.//]
|
|
// TESTRESPONSE[s/: [0-9]+/: $body.$_path/]
|