https://pizza.rs/tags/wildcard/Recent content in Wildcard on INFINI PizzaHugoenhttps://pizza.rs/docs/references/search/term-level/wildcard/Mon, 01 Jan 0001 00:00:00 +0000https://pizza.rs/docs/references/search/term-level/wildcard/<h1 id="wildcard-query"> Wildcard query <a class="anchor" href="#wildcard-query">#</a> </h1> <p>Returns documents that contain terms matching a wildcard pattern. The pattern supports <code>*</code> (any sequence of characters, including none) and <code>?</code> (any single character).</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 pattern is expanded against the inverted index&rsquo;s <strong>term dictionary</strong>: the engine walks the field&rsquo;s terms, keeps those matching the pattern, and unions their postings lists — the same result as a <code>should</code> of <a href="https://pizza.rs/docs/references/search/term-level/term/"><code>term</code></a> queries over the surviving terms. Matching is anchored at both ends: <code>web-1</code> is the whole term, so <code>web-*</code> matches <code>web-10</code> and <code>web-1</code> itself, but <code>*web-1*</code> is required for anything with text on both sides.</p>