Field parameters on INFINI Pizza

Analysis parameters

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

Analysis parameters #

`analyzer` #

The analyzer used for indexing.

Carried by: text.

`search_analyzer` #

The analyzer used for searching.

Carried by: text.

`normalizer` #

For keyword fields — a single normalizer (e.g. lowercase, trim, unicode_nfkc) applied to the value before it is indexed, so term queries match case-insensitively; the _source keeps the original. See the normalizer catalog.

Carried by: keyword.

Indexing parameters

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

Indexing parameters #

`index` #

For non-object fields, if set, Pizza would build an index for the field to make it searchable. For object fields, the index parameter overrides the index settings of its sub-fields.

Carried by: most scalar types and object — see each field type. Not carried by the vector types.

`index_options` #

Controls what information is added to the inverted index. Available options are:

docs: Only the doc number is indexed. Can answer the question Does this term exist in this field?
freqs: Doc number and term frequencies are indexed. Term frequencies are used to score repeated terms higher than single terms.
positions (default): Doc number, term frequencies, and term positions (or order) are indexed. Positions can be used for proximity or phrase queries.
offsets: Doc number, term frequencies, positions, and start and end character offsets (which map the term back to the original string) are indexed. Offsets are used by the unified highlighter to speed up highlighting.

Carried by: text, keyword.

Storage layout parameters

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

Storage layout parameters #

`source`, `column`, `store` #

Per-field storage placement booleans. Every field is included in the _source blob by default; set source: false to drop it from stored docs. column keeps the value as a compressed doc-values column (fast retrieval and aggregation) — it defaults to the field’s profile layout, which turns it on for column-friendly types (numbers, dates, keywords) and off for analyzed text. store keeps a separate document-store copy for fast field retrieval (default false).

Realtime and in-place parameters

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

Realtime and in-place parameters #

`realtime` #

For non-object fields, enabling this option allows the field to support real-time search. For object fields, the realtime parameter overrides the realtime settings of its sub-fields.

Carried by: every type — see each field type.

`inplace` #

For non-object numeric and boolean fields, enabling this option makes a dedicated column the authoritative store of the field’s value. Partial updates on such fields can be applied as O(1) in-place column writes instead of rebuilding the document, which keeps frequent counters and flags cheap — only some update operators qualify, and the whole request must target inplace fields; see fast-lane eligibility for the exact operator list and conditions. A partial update that mixes inplace fields with regular fields is supported as well, and the document keeps its _id either way. Values are visible the moment the write lands (search snapshots pin the document set, not the values); a missing numeric field starts from 0 and a missing boolean from false; integer arithmetic wraps on overflow. See In-place columns for the visibility, arithmetic, and query-pruning semantics.

Structural parameters

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

Structural parameters #

`properties` #

Nested sub-fields, for object-shaped types.

Carried by: object, nested.

`fields` #

It is often useful to index the same field in different ways for different purposes. This is the purpose of multi-fields.

A dense_vector sub-field gets a derived meaning — semantic wiring: declare it with vector_options.model + dims on a top-level text/keyword field and the parent’s text is embedded server-side at write time (the source is implicitly the parent and must not be set explicitly; the model must resolve to a configured embedding endpoint). See the declarative form.

Type-specific parameters

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

Type-specific parameters #

Parameters bound to a single type family.

`format` #

For date fields, the accepted input format(s) — default strict_date_optional_time||epoch_millis; multiple formats join with ||.

Carried by: date.

`vector_options` #

For vector fields — dims, similarity, index_type (flat, HNSW, BBQ or TurboQuant variants), plus tuning knobs (m, ef_construction, ef_search) and, for declarative semantic embedding, model, source and service (the AI-service disambiguator when several services list the same model id). The full catalog lives on the vector search page; the semantic_text type is the sugar form over the same wiring.

Field parameters on INFINI Pizza

Analysis parameters

Analysis parameters #

analyzer #

search_analyzer #

normalizer #

Indexing parameters

Indexing parameters #

index #

index_options #

Storage layout parameters

Storage layout parameters #

source, column, store #

Realtime and in-place parameters

Realtime and in-place parameters #

realtime #

inplace #

Structural parameters

Structural parameters #

properties #

fields #

Type-specific parameters

Type-specific parameters #

format #

vector_options #

`analyzer` #

`search_analyzer` #

`normalizer` #

`index` #

`index_options` #

`source`, `column`, `store` #

`realtime` #

`inplace` #

`properties` #

`fields` #

`format` #

`vector_options` #