Skip to content

[Backport 3.1] Highlight support for wildcard field #10708

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
Aug 11, 2025
Merged

[Backport 3.1] Highlight support for wildcard field #10708

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
6 changes: 6 additions & 0 deletions _field-types/supported-field-types/wildcard.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -22,6 +22,9 @@ At search time, required substrings from the query pattern are matched against t
In general, exact match queries (like [`term`]({{site.url}}{{site.baseurl}}/query-dsl/term/term/) or [`terms`]({{site.url}}{{site.baseurl}}/query-dsl/term/term/) queries) perform less effectively on `wildcard` fields than on `keyword` fields, while [`wildcard`]({{site.url}}{{site.baseurl}}/query-dsl/term/wildcard/), [`prefix`]({{site.url}}{{site.baseurl}}/query-dsl/term/prefix/), and [`regexp`]({{site.url}}{{site.baseurl}}/query-dsl/term/regexp/) queries perform better on `wildcard` fields.
{: .tip}

Wildcard fields do not support highlighting.
{: .note}

## Example

Create a mapping with a `wildcard` field:
Expand All @@ -40,6 +43,9 @@ PUT logs
```
{% include copy-curl.html %}

All queries on wildcard fields have a constant score---usually `1`. You can override the constant score using the `boost` parameter.
{: .note}

## Parameters

The following table lists all parameters available for `wildcard` fields.
Expand Down