mirror of
https://github.com/elastic/elasticsearch.git
synced 2025-06-29 09:54:06 -04:00
Most aggregations (terms, histogram, stats, percentiles, geohash-grid) now support a new `missing` option which defines the value to consider when a field does not have a value. This can be handy if you eg. want a terms aggregation to handle the same way documents that have "N/A" or no value for a `tag` field. This works in a very similar way to the `missing` option on the `sort` element. One known issue is that this option sometimes cannot make the right decision in the unmapped case: it needs to replace all values with the `missing` value but might not know what kind of values source should be produced (numerics, strings, geo points?). For this reason, we might want to add an `unmapped_type` option in the future like we did for sorting. Related to #5324 |
||
---|---|---|
.. | ||
children-aggregation.asciidoc | ||
datehistogram-aggregation.asciidoc | ||
daterange-aggregation.asciidoc | ||
filter-aggregation.asciidoc | ||
filters-aggregation.asciidoc | ||
geodistance-aggregation.asciidoc | ||
geohashgrid-aggregation.asciidoc | ||
global-aggregation.asciidoc | ||
histogram-aggregation.asciidoc | ||
iprange-aggregation.asciidoc | ||
missing-aggregation.asciidoc | ||
nested-aggregation.asciidoc | ||
range-aggregation.asciidoc | ||
reverse-nested-aggregation.asciidoc | ||
sampler-aggregation.asciidoc | ||
significantterms-aggregation.asciidoc | ||
terms-aggregation.asciidoc |