2015-05-01 16:04:55 -04:00
|
|
|
[[search-aggregations-bucket]]
|
|
|
|
|
== Bucket Aggregations
|
|
|
|
|
|
|
|
|
|
Bucket aggregations don't calculate metrics over fields like the metrics aggregations do, but instead, they create
|
|
|
|
|
buckets of documents. Each bucket is associated with a criterion (depending on the aggregation type) which determines
|
|
|
|
|
whether or not a document in the current context "falls" into it. In other words, the buckets effectively define document
|
|
|
|
|
sets. In addition to the buckets themselves, the `bucket` aggregations also compute and return the number of documents
|
2016-04-21 10:16:45 -04:00
|
|
|
that "fell into" each bucket.
|
2015-05-01 16:04:55 -04:00
|
|
|
|
|
|
|
|
Bucket aggregations, as opposed to `metrics` aggregations, can hold sub-aggregations. These sub-aggregations will be
|
|
|
|
|
aggregated for the buckets created by their "parent" bucket aggregation.
|
|
|
|
|
|
|
|
|
|
There are different bucket aggregators, each with a different "bucketing" strategy. Some define a single bucket, some
|
|
|
|
|
define fixed number of multiple buckets, and others dynamically create the buckets during the aggregation process.
|
|
|
|
|
|
2017-01-23 05:18:30 -05:00
|
|
|
include::bucket/adjacency-matrix-aggregation.asciidoc[]
|
|
|
|
|
|
2015-05-01 16:04:55 -04:00
|
|
|
include::bucket/children-aggregation.asciidoc[]
|
|
|
|
|
|
|
|
|
|
include::bucket/datehistogram-aggregation.asciidoc[]
|
|
|
|
|
|
|
|
|
|
include::bucket/daterange-aggregation.asciidoc[]
|
|
|
|
|
|
2015-12-14 06:54:41 -05:00
|
|
|
include::bucket/diversified-sampler-aggregation.asciidoc[]
|
|
|
|
|
|
2015-05-01 16:04:55 -04:00
|
|
|
include::bucket/filter-aggregation.asciidoc[]
|
|
|
|
|
|
|
|
|
|
include::bucket/filters-aggregation.asciidoc[]
|
|
|
|
|
|
|
|
|
|
include::bucket/geodistance-aggregation.asciidoc[]
|
|
|
|
|
|
|
|
|
|
include::bucket/geohashgrid-aggregation.asciidoc[]
|
|
|
|
|
|
|
|
|
|
include::bucket/global-aggregation.asciidoc[]
|
|
|
|
|
|
|
|
|
|
include::bucket/histogram-aggregation.asciidoc[]
|
|
|
|
|
|
|
|
|
|
include::bucket/iprange-aggregation.asciidoc[]
|
|
|
|
|
|
|
|
|
|
include::bucket/missing-aggregation.asciidoc[]
|
|
|
|
|
|
|
|
|
|
include::bucket/nested-aggregation.asciidoc[]
|
|
|
|
|
|
|
|
|
|
include::bucket/range-aggregation.asciidoc[]
|
|
|
|
|
|
|
|
|
|
include::bucket/reverse-nested-aggregation.asciidoc[]
|
|
|
|
|
|
|
|
|
|
include::bucket/sampler-aggregation.asciidoc[]
|
|
|
|
|
|
|
|
|
|
include::bucket/significantterms-aggregation.asciidoc[]
|
|
|
|
|
|
2017-05-24 08:46:43 -04:00
|
|
|
include::bucket/significanttext-aggregation.asciidoc[]
|
|
|
|
|
|
2015-05-01 16:04:55 -04:00
|
|
|
include::bucket/terms-aggregation.asciidoc[]
|
|
|
|
|
|
Add composite aggregator (#26800)
* This change adds a module called `aggs-composite` that defines a new aggregation named `composite`.
The `composite` aggregation is a multi-buckets aggregation that creates composite buckets made of multiple sources.
The sources for each bucket can be defined as:
* A `terms` source, values are extracted from a field or a script.
* A `date_histogram` source, values are extracted from a date field and rounded to the provided interval.
This aggregation can be used to retrieve all buckets of a deeply nested aggregation by flattening the nested aggregation in composite buckets.
A composite buckets is composed of one value per source and is built for each document as the combinations of values in the provided sources.
For instance the following aggregation:
````
"test_agg": {
"terms": {
"field": "field1"
},
"aggs": {
"nested_test_agg":
"terms": {
"field": "field2"
}
}
}
````
... which retrieves the top N terms for `field1` and for each top term in `field1` the top N terms for `field2`, can be replaced by a `composite` aggregation in order to retrieve **all** the combinations of `field1`, `field2` in the matching documents:
````
"composite_agg": {
"composite": {
"sources": [
{
"field1": {
"terms": {
"field": "field1"
}
}
},
{
"field2": {
"terms": {
"field": "field2"
}
}
},
}
}
````
The response of the aggregation looks like this:
````
"aggregations": {
"composite_agg": {
"buckets": [
{
"key": {
"field1": "alabama",
"field2": "almanach"
},
"doc_count": 100
},
{
"key": {
"field1": "alabama",
"field2": "calendar"
},
"doc_count": 1
},
{
"key": {
"field1": "arizona",
"field2": "calendar"
},
"doc_count": 1
}
]
}
}
````
By default this aggregation returns 10 buckets sorted in ascending order of the composite key.
Pagination can be achieved by providing `after` values, the values of the composite key to aggregate after.
For instance the following aggregation will aggregate all composite keys that sorts after `arizona, calendar`:
````
"composite_agg": {
"composite": {
"after": {"field1": "alabama", "field2": "calendar"},
"size": 100,
"sources": [
{
"field1": {
"terms": {
"field": "field1"
}
}
},
{
"field2": {
"terms": {
"field": "field2"
}
}
}
}
}
````
This aggregation is optimized for indices that set an index sorting that match the composite source definition.
For instance the aggregation above could run faster on indices that defines an index sorting like this:
````
"settings": {
"index.sort.field": ["field1", "field2"]
}
````
In this case the `composite` aggregation can early terminate on each segment.
This aggregation also accepts multi-valued field but disables early termination for these fields even if index sorting matches the sources definition.
This is mandatory because index sorting picks only one value per document to perform the sort.
2017-11-16 09:13:36 -05:00
|
|
|
include::bucket/composite-aggregation.asciidoc[]
|
|
|
|
|
|
