https://pizza.rs/tags/highlight/Recent content in Highlight on INFINI PizzaHugoenhttps://pizza.rs/docs/references/search/request/highlight/Mon, 01 Jan 0001 00:00:00 +0000https://pizza.rs/docs/references/search/request/highlight/<h1 id="highlighting"> Highlighting <a class="anchor" href="#highlighting">#</a> </h1> <p>Ask for matched fragments of your text fields back alongside each hit, with the matched terms wrapped in tags — ready to render as a search result list.</p> <div class="highlight"><pre tabindex="0" class="chroma"><code class="language-sh" data-lang="sh"><span class="line"><span class="cl">POST /my-collection/_search </span></span></code></pre></div><h2 id="how-it-works"> How it works <a class="anchor" href="#how-it-works">#</a> </h2> <p>Highlighting is an engine-native enrich step that runs on the returned page only — after ranking and truncation, exactly like <a href="https://pizza.rs/docs/references/search/request/script-fields/">script fields</a>. It has two phases (<code>lib/engine/src/search/highlight/</code>):</p> <p><strong>1. Term extraction.</strong> The engine walks the query tree and collects <code>(field, term)</code> pairs worth highlighting: <code>term</code>, <code>terms</code>, <code>fuzzy</code>, <code>span_term</code>, <code>intervals</code>, <code>match</code>, <code>multi_match</code>, <code>match_phrase</code>, and <code>bool</code> clauses. Text queries (<code>match</code>, <code>multi_match</code>, <code>phrase</code>) are re-tokenized through the field&rsquo;s search analyzer (or the query&rsquo;s explicit <code>analyzer</code> override), so the highlighted terms mirror what the query scored. <code>must_not</code> clauses never contribute — documents excluded by them get no tags from them. <code>match_all</code>, <code>range</code>, <code>geo</code> and <code>vector</code> queries carry nothing to highlight.</p>