aggregations.asciidoc 1.5 KB

123456789101112131415161718192021222324252627282930313233
  1. [[breaking_50_aggregations_changes]]
  2. === Aggregation changes
  3. ==== Significant terms on numeric fields
  4. Numeric fields have been refactored to use a different data structure that
  5. performs better for range queries. However, since this data structure does
  6. not record document frequencies, numeric fields need to fall back to running
  7. queries in order to estimate the number of matching documents in the
  8. background set, which may incur a performance degradation.
  9. It is recommended to use <<keyword,`keyword`>> fields instead, either directly
  10. or through a <<multi-fields,multi-field>> if the numeric representation is
  11. still needed for sorting, range queries or numeric aggregations like
  12. <<search-aggregations-metrics-stats-aggregation,`stats` aggregations>>.
  13. ==== `ip_range` aggregations
  14. Now that Elasticsearch supports `ipv6`, `ip` addresses are encoded in the index
  15. using a binary representation rather than a numeric representation. As a
  16. consequence, the output of `ip_range` aggregations does not give numeric values
  17. for `from` and `to` anymore.
  18. ==== `size: 0` on Terms, Significant Terms and Geohash Grid Aggregations
  19. `size: 0` is no longer valid for the terms, significant terms and geohash grid
  20. aggregations. Instead a size should be explicitly specified with a number greater
  21. than zero.
  22. ==== Fractional time values
  23. Fractional time values (e.g., 0.5s) are no longer supported. For example, this means when setting
  24. date histogram intervals "1.5h" will be rejected and should instead be input as "90m".