https://pizza.rs/tags/composite/Recent content in Composite on INFINI PizzaHugoenhttps://pizza.rs/docs/references/aggregation/bucket/composite/Mon, 01 Jan 0001 00:00:00 +0000https://pizza.rs/docs/references/aggregation/bucket/composite/<h1 id="composite-aggregation"> Composite aggregation <a class="anchor" href="#composite-aggregation">#</a> </h1> <p>Paginated multi-source bucket aggregation: the composite key is a tuple built from several sources (a <code>terms</code> field, a <code>histogram</code> interval, a <code>date_histogram</code>, a <code>geotile_grid</code>), and pages are pulled with an <code>after</code> cursor. It does what a single <a href="https://pizza.rs/docs/references/aggregation/bucket/terms/"><code>terms</code></a> cannot: group by several dimensions at once, and stream <em>all</em> combinations without oversizing <code>size</code>.</p> <h2 id="how-it-works"> How it works <a class="anchor" href="#how-it-works">#</a> </h2> <p>Each entry in <code>sources</code> is named: <code>{ &quot;day&quot;: { … } }</code> binds <code>day</code> to one dimension of the composite key. A bucket&rsquo;s <code>key</code> maps each source name to its value; buckets come back in ascending key order — first source most significant, values compared as numbers when both are (numbers sort before strings), as strings otherwise.</p>