mirror of
https://github.com/elastic/elasticsearch.git
synced 2025-06-30 02:13:33 -04:00
* Docs: Refine note about `after_key` I was curious about composite aggregations, specifically I wanted to know how to write a composite aggregation that had all of its buckets filtered out so you *had* to use the `after_key`. Then I saw that we've declared composite aggregations not to work with pipelines in #44180. So I'm not sure you *can* do that any more. Which makes the note about `after_key` inaccurate. This rejiggers that section of the docs a little so it is more obvious that you send the `after_key` back to us. And so it is more obvious that you should *only* use the `after_key` that we give you rather than try to work it out for yourself. * Apply suggestions from code review Co-Authored-By: James Rodewig <james.rodewig@elastic.co> Co-authored-by: James Rodewig <james.rodewig@elastic.co> |
||
---|---|---|
.. | ||
adjacency-matrix-aggregation.asciidoc | ||
autodatehistogram-aggregation.asciidoc | ||
children-aggregation.asciidoc | ||
composite-aggregation.asciidoc | ||
datehistogram-aggregation.asciidoc | ||
daterange-aggregation.asciidoc | ||
diversified-sampler-aggregation.asciidoc | ||
filter-aggregation.asciidoc | ||
filters-aggregation.asciidoc | ||
geodistance-aggregation.asciidoc | ||
geohashgrid-aggregation.asciidoc | ||
geotilegrid-aggregation.asciidoc | ||
global-aggregation.asciidoc | ||
histogram-aggregation.asciidoc | ||
iprange-aggregation.asciidoc | ||
missing-aggregation.asciidoc | ||
nested-aggregation.asciidoc | ||
parent-aggregation.asciidoc | ||
range-aggregation.asciidoc | ||
range-field-note.asciidoc | ||
rare-terms-aggregation.asciidoc | ||
reverse-nested-aggregation.asciidoc | ||
sampler-aggregation.asciidoc | ||
significantterms-aggregation.asciidoc | ||
significanttext-aggregation.asciidoc | ||
terms-aggregation.asciidoc |