https://pizza.rs/tags/fuzzy/Recent content in Fuzzy on INFINI PizzaHugoenhttps://pizza.rs/docs/references/search/term-level/fuzzy/Mon, 01 Jan 0001 00:00:00 +0000https://pizza.rs/docs/references/search/term-level/fuzzy/<h1 id="fuzzy-query"> Fuzzy query <a class="anchor" href="#fuzzy-query">#</a> </h1> <p>Returns documents that contain terms similar to the search term, within the maximum edit distance (Levenshtein — with transpositions counting as a single edit by default).</p> <p>Use it when the indexed terms are only approximately known: typos in identifiers, OCR noise, or human-entered names.</p> <blockquote> <p><strong>Inside a <a href="https://pizza.rs/docs/references/search/relational/nested/"><code>nested</code></a> query:</strong> not supported yet — the clause is rejected with an HTTP 400 naming the offending clause.</p> </blockquote> <h2 id="how-it-works"> How it works <a class="anchor" href="#how-it-works">#</a> </h2> <p>The value is expanded against the inverted index&rsquo;s <strong>term dictionary</strong> by edit distance, then the survivors&rsquo; postings are unioned like a <code>should</code> of <a href="https://pizza.rs/docs/references/search/term-level/term/"><code>term</code></a> queries. The engine takes the <strong>union</strong> of three resolution passes — the value recorded as an exact term, a whole-value fuzzy walk, and (on non-keyword fields) a per-token walk after running the field&rsquo;s search analyzer over the value — so the query works on keyword fields and on analyzed text alike (the per-token pass matters for CJK and multi-word input). On <code>keyword</code> fields the raw value is used, with the field&rsquo;s normalizer applied first and no tokenization.</p>