Term-level queries on INFINI Pizza

Term query

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

Term query #

Returns documents that contain an exact term in a provided field.

You can use the term query to find documents based on a precise value such as a price, a product ID, or a username.

Inside a nested query: supported — the value is matched per array element. On text fields prefer match; term targets exact keyword / numeric / date values.

Examples #

GET /_search
{
 "query": {
 "term": {
 "field": "org.id",
 "value": "infini"
 }
 }
}

Parameters for `term` #

field
(Required, string) Field you wish to search.
value
(Required, string) Term you wish to find in the provided field. To return a document, the term must exactly match the field value, including whitespace and capitalization.
case_insensitive
(Optional, boolean) Allows ASCII case insensitive matching of the value with the indexed field values when set to true. Default is false.
boost
(Optional, float, default: 1.0) Decrease or increase the relevance scores of the query.

Terms query

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

Terms query #

Returns documents that contain one or more exact terms in a provided field. Equivalent to a boolean should of individual term queries — a document matches if it contains any of the values.

Inside a nested query: not supported yet — the clause is rejected with an HTTP 400 naming the offending clause. Expand into a bool should of term clauses instead.

Examples #

POST /my-collection/_search
{
 "query": {
 "terms": {
 "field": "status",
 "values": ["published", "pending"]
 }
 }
}

Parameters for `terms` #

field
(Required, string) The field to match.
values
(Required, array) List of terms to match. A document matches if it contains any of these values.
boost
(Optional, float, default: 1.0) Decrease or increase the relevance scores of the query.

Notes #

The values are matched as exact terms — no analysis is applied. To match analyzed text, use the match query.

Prefix query

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

Prefix query #

Returns documents that contain a specific prefix in a provided field.

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

Examples #

The following search returns documents where the org.id field contains a term that begins with inf.

GET /_search
{
 "query": {
 "prefix": {
 "field": "org.id",
 "value": "inf"
 }
 }
}

Parameters for `prefix` #

field
(Required, string) Field you wish to search.
value
(Required, string) Beginning characters of terms you wish to find in the provided field.
case_insensitive
(Optional, boolean) Allows ASCII case insensitive matching of the value with the indexed field values when set to true. Default is false.
boost
(Optional, float, default: 1.0) Decrease or increase the relevance scores of the query.
rewrite
(Optional, string) Method used to rewrite the expanded terms (constant_score, scoring_boolean, top_terms_N, …).

Fuzzy query

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

Fuzzy query #

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).

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

Examples #

"AUTO" picks the budget from the value’s length — serch is 5 characters, so AUTO grants a single edit, which is exactly the insertion needed to reach search:

Wildcard query

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

Wildcard query #

Returns documents that contain terms matching a wildcard pattern. The pattern supports * (any sequence of characters, including none) and ? (any single character).

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": {
 "wildcard": {
 "field": "user.id",
 "value": "ki*y"
 }
 }
}

Parameters for `wildcard` #

<field>
(Required, string) Field you wish to search.
value
(Required, string) Wildcard pattern to match terms in the provided <field> against. Note: leading wildcards (*foo) are expensive — prefer the prefix query when possible.
case_insensitive
(Optional, boolean, default: false) ASCII case-insensitive matching of the value with the indexed field values.
boost
(Optional, float, default: 1.0) Decrease or increase the relevance scores of the query.
rewrite
(Optional, string) Method used to rewrite the expanded terms (constant_score, scoring_boolean, …).

Regexp query

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

Regexp query #

Returns documents that contain terms matching a regular expression.

A regular expression is a way to match patterns in data using placeholder characters, called operators. For a list of operators supported by the regexp query, see Regular expression syntax.

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

Examples #

The following search returns documents where the org.id field contains any term that begins with in and ends with y. The .* operators match any characters of any length, including no characters. Matching terms can include ini, inni, and infini.

Suffix query

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

Suffix query #

Returns documents that contain terms ending in the provided value. This is the mirror of the prefix query; like a leading wildcard, it is more expensive than a prefix match.

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": {
 "suffix": {
 "field": "url.path",
 "value": ".jpg"
 }
 }
}

Parameters for `suffix` #

<field>
(Required, string) Field you wish to search.
value
(Required, string) The suffix terms must end with.
case_insensitive
(Optional, boolean, default: false) ASCII case-insensitive matching of the value with the indexed field values.
boost
(Optional, float, default: 1.0) Decrease or increase the relevance scores of the query.
rewrite
(Optional, string) Method used to rewrite the query (constant_score, scoring_boolean, …).

Range query

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

Range query #

Returns documents that contain terms within a provided range.

Inside a nested query: supported — the bounds apply per array element.

Examples #

The following search returns the sales whose price is between 45 and 60 — 20 of the 120 documents in the sales dataset.

GET /_search
{
 "query": {
 "range": {
 "field": "age",
 "gte": 10,
 "lte": 20
 }
 }
}

Parameters for `range` #

field
(Required, string) Field you wish to search.
gt
(Optional) Greater than.
gte
(Optional) Greater than or equal to.
lt
(Optional) Less than.
lte
(Optional) Less than or equal to.
format
(Optional, string) Date format for date-field range bounds.
time_zone
(Optional, string) Time zone for date-field range bounds, e.g. +08:00.
boost
(Optional, float, default: 1.0) Decrease or increase the relevance scores of the query.
relation
(Optional, string) How the range matches range-typed fields: INTERSECTS (default), CONTAINS, or WITHIN.

Exists query

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

Exists query #

Returns documents that contain an indexed value for a specific field.

A document matches when the field has at least one non-null value — an empty string or an empty array does not count as existing.

Inside a nested query: supported — matches elements that carry the field.

Examples #

POST /my-collection/_search
{
 "query": {
 "exists": {
 "field": "user"
 }
 }
}

Parameters for `exists` #

field
(Required, string) Field you wish to check for presence.

Term-level queries on INFINI Pizza

Term query

Term query #

Examples #

Parameters for term #

Terms query

Terms query #

Examples #

Parameters for terms #

Notes #

Prefix query

Prefix query #

Examples #

Parameters for prefix #

Fuzzy query

Fuzzy query #

Examples #

Wildcard query

Wildcard query #

Examples #

Parameters for wildcard #

Regexp query

Regexp query #

Examples #

Suffix query

Suffix query #

Examples #

Parameters for suffix #

Range query

Range query #

Examples #

Parameters for range #

Exists query

Exists query #

Examples #

Parameters for exists #

Parameters for `term` #

Parameters for `terms` #

Parameters for `prefix` #

Parameters for `wildcard` #

Parameters for `suffix` #

Parameters for `range` #

Parameters for `exists` #