<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Significant_terms on INFINI Pizza</title><link>https://pizza.rs/tags/significant_terms/</link><description>Recent content in Significant_terms on INFINI Pizza</description><generator>Hugo</generator><language>en</language><atom:link href="https://pizza.rs/tags/significant_terms/index.xml" rel="self" type="application/rss+xml"/><item><title>Significant terms aggregation</title><link>https://pizza.rs/docs/references/aggregation/bucket/significant-terms/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://pizza.rs/docs/references/aggregation/bucket/significant-terms/</guid><description>&lt;h1 id="significant-terms-aggregation">
 Significant terms aggregation
 &lt;a class="anchor" href="#significant-terms-aggregation">#&lt;/a>
&lt;/h1>
&lt;p>A multi-bucket aggregation returning terms that are unusually frequent
in the current scope (foreground) compared with the whole index
(background) — the classic &amp;ldquo;what&amp;rsquo;s special about this subset&amp;rdquo; query.&lt;/p>
&lt;p>In this engine &lt;code>significant_terms&lt;/code> currently approximates that idea by
foreground frequency: it ranks the scope&amp;rsquo;s values by their in-scope
&lt;code>doc_count&lt;/code>, without computing background statistics. Nest it under a
query or a parent bucket to scope the foreground set; the values that
dominate that scope come out on top.&lt;/p></description></item></channel></rss>