Request-level options on INFINI Pizza

Sort and pagination

Mon, 01 Jan 0001 00:00:00 +0000

Sort and pagination #

Control which documents come back and in what order — sort, from/size, search_after/search_before, and total-hit accounting.

POST /my-collection/_search

Sort #

sort is an array of sort clauses evaluated in order; the first clause that produces a difference decides the order.

Parameters #

field
(Required, string) The field to sort by. Two pseudo-fields are always available: _score (relevance, descending by default) and _doc (index order — the cheapest possible sort).
order
(Optional, asc | desc) Sort direction. When omitted the engine sorts descending for _score and ascending for regular fields.
missing
(Optional, first | last; the gateway also accepts the Elasticsearch spellings _first / _last) Where documents without a value for the field land, independent of the sort direction. Default: last. Documents whose keys tie (including two missing values) break the tie by internal doc order, so pages are repeatable.

Sorting on an indexed field lets the engine skip documents that cannot make the cut (early termination); "_doc" and index-time sorted fields (see field parameters) are the fastest.

Highlighting

Mon, 01 Jan 0001 00:00:00 +0000

Highlighting #

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.

POST /my-collection/_search

Example #

{
 "query": { "match": { "field": "message", "query": "search" } },
 "highlight": {
 "fields": {
 "message": {
 "fragment_size": 100,
 "number_of_fragments": 3
 }
 }
 },
 "size": 5
}

Each returned hit carries a highlight object whose keys are the requested fields; values are fragment strings with matched terms wrapped in the tags (default <em> … </em>). Custom tags — same idea with <b> wrapping:

Hybrid search and scoring pipeline

Mon, 01 Jan 0001 00:00:00 +0000

Hybrid search and scoring pipeline #

Pizza runs lexical (BM25) and vector retrieval side by side and gives you explicit, composable stages to combine and re-shape scores:

retrieve → fuse → score_functions → rescore
(parallel (merge (function (second pass
 retrievers) the lists) scoring) on the top window)

Every stage is optional and combines with a plain query: use score_functions alone on a keyword search, or the full chain for hybrid retrieval.

Field collapsing

Mon, 01 Jan 0001 00:00:00 +0000

Field collapsing #

Collapse the result list so each distinct value of a field appears at most once — “best product per merchant”, “best article per author” — without a terms aggregation, keeping full hit semantics (scores, source, highlight).

POST /my-collection/_search

Example #

One best-selling hit per product type (the dataset has four: hat, t-shirt, mug, sticker); the plain match-all total stays 120 — collapse deduplicates the RESULT list, not the count.

Streaming search

Mon, 01 Jan 0001 00:00:00 +0000

Streaming #

Search on Pizza is real-time — documents are visible the moment they are written. The stream block makes a single search request behave like a subscription: the engine keeps the query warm and pushes fresh hits as they land, instead of making the client poll.

POST /my-collection/_search

Example #

This page has no live playground demo: the response body here is a live HTTP stream (chunked, newline-delimited hits), while the in-page widget executes one-shot queries against a WebAssembly engine and renders a complete JSON result. Run the example with curl against a live server to watch chunks arrive incrementally.