Full-text queries on INFINI Pizza

Match query

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

Match query #

Returns documents that match a provided text, number, date or boolean value. The provided text is analyzed before matching — this is the primary full-text query.

Inside a nested query: supported — the text is matched per array element.

Examples #

POST /my-collection/_search
{
 "query": {
 "match": {
 "field": "message",
 "query": "this is a test"
 }
 }
}

The match query applies the field’s search analyzer (or analyzer when given) to the text, then matches the resulting tokens with OR semantics by default. Require all tokens with operator:

Match phrase query

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

Match phrase query #

Returns documents that contain the exact sequence of terms, in order, with no other terms in between (modulo slop). The text is analyzed before matching, like the match query.

Inside a nested query: supported — the phrase, including its slop, must be satisfied by ONE array element; terms keep query order.

Examples #

POST /my-collection/_search
{
 "query": {
 "match_phrase": {
 "field": "message",
 "query": "this is a test"
 }
 }
}

Allow words in between with slop:

Multi-match query

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

Multi-match query #

Returns documents that match a provided text across several fields — like the match query, with per-field boosts and multi-field scoring strategies.

Inside a nested query: supported — fields under the nested path are matched per array element.

Examples #

POST /my-collection/_search
{
 "query": {
 "multi_match": {
 "query": "search engine",
 "fields": ["title^3", "description"]
 }
 }
}

Parameters for `multi_match` #

query
(Required, string) The query text to search for.
fields
(Required, array of strings) Fields to search, with optional per-field boosts via the field^boost syntax (e.g. "title^3").
type
(Optional, string) Match type / multi-field scoring strategy: best_fields (default — score of the best-matching field, plus tie_breaker times the others), most_fields (sum) or cross_fields.
operator
(Optional, string, default: or) Boolean operator joining terms within each field: or or and.
minimum_should_match
(Optional, string) Minimum number of should clauses that must match. Defaults to 1 (at least one field must match).
analyzer
(Optional, string) Analyzer override forwarded to the per-field match queries.
tie_breaker
(Optional, float, default: 0) Tie-breaker multiplier for best_fields: score from the best-matching field plus tie_breaker * score from the other fields.
boost
(Optional, float, default: 1.0) Boost applied to the overall query.
type (wire alias match_type)
(Optional, string) Multi-field scoring strategy: best_fields (max score across fields, default), most_fields (sum), cross_fields, phrase, phrase_prefix.

Query string query

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

Query string query #

Returns documents that match a compact query-syntax string, e.g. status:active AND title:search. The same parser powers the URI search parameter ?q=.

Inside a nested query: not supported yet — the clause is rejected with an HTTP 400 naming the offending clause.

Examples #

POST /my-collection/_search
{
 "query": {
 "query_string": {
 "query": "status:active AND title:search"
 }
 }
}

Across several fields with per-field boosts:

Boolean query

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

Boolean query #

A query that matches documents matching boolean combinations of other queries. It is built using one or more boolean clauses.

Inside a nested query: supported — must/filter/should/must_not and minimum_should_match all apply within ONE array element; clauses matched by different elements never combine.

Examples #

POST /my-collection/_search
{
 "query": {
 "bool": {
 "must": [
 { "match": { "field": "title", "query": "search" } }
 ],
 "filter": [
 { "term": { "field": "status", "value": "published" } }
 ],
 "must_not": [
 { "range": { "field": "views", "gte": 100000 } }
 ],
 "should": [
 { "term": { "field": "tags", "value": "featured" } }
 ],
 "minimum_should_match": 1
 }
 }
}

Clause types #

must
The document must match. Contributes to the score.
filter
The document must match. Does not contribute to the score — results may be cached by filter context.
should
The document should match. Contributes to the score; required to match only when no must/filter clauses are present (then at least one should must match) or when minimum_should_match is set.
must_not
The document must not match. Does not contribute to the score.

Parameters for `bool` #

minimum_should_match
(Optional, integer) Minimum number of should clauses a document must match. The built-in default is 1 when the query has should clauses but no must/filter, otherwise 0.
score_mode
(Optional, string) Multi-field score combination strategy for should clauses: most_fields (sum — the default, for backward compatibility) or best_fields (max, dis_max style).
tie_breaker
(Optional, float, default: 0) Tie-breaker for best_fields mode. Final score: max_score + tie_breaker * sum(other_scores). Range [0, 1].
combination_strategy
(Optional, string) Score combination strategy for should clauses across fields (best_fields or most_fields).

Match all query

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

Match all query #

Matches every document. This is the default query used when no query is sent in a search request.

Examples #

POST /my-collection/_search
{
 "query": {
 "match_all": {}
 }
}

Parameters for `match_all` #

boost
(Optional, float, default: 1.0) Applied to every matched document’s score.

Match none query #

The counterpart match_none matches no document at all:

Span queries

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

Span queries #

Span queries are low-level positional queries that expose and control the positions of terms — the building blocks for phrase-adjacent logic that match_phrase does not express directly. Most use cases are better served by match_phrase (or its slop); the span family exists for the remaining ones.

Inside a nested query: not supported yet — span clauses are rejected with an HTTP 400 naming the offending clause. Use match_phrase with slop for positional logic.

Full-text queries on INFINI Pizza

Match query

Match query #

Examples #

Match phrase query

Match phrase query #

Examples #

Multi-match query

Multi-match query #

Examples #

Parameters for multi_match #

Query string query

Query string query #

Examples #

Boolean query

Boolean query #

Examples #

Clause types #

Parameters for bool #

Match all query

Match all query #

Examples #

Parameters for match_all #

Match none query #

Span queries

Span queries #

Parameters for `multi_match` #

Parameters for `bool` #

Parameters for `match_all` #