Skip to content

Commit e69d97d

Browse files
Highlight support for wildcard field (#10707) (#10708)
1 parent 0cb17ac commit e69d97d

File tree

1 file changed

+6
-0
lines changed

1 file changed

+6
-0
lines changed

_field-types/supported-field-types/wildcard.md

Lines changed: 6 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -22,6 +22,9 @@ At search time, required substrings from the query pattern are matched against t
2222
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.
2323
{: .tip}
2424

25+
Wildcard fields do not support highlighting.
26+
{: .note}
27+
2528
## Example
2629

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

46+
All queries on wildcard fields have a constant score---usually `1`. You can override the constant score using the `boost` parameter.
47+
{: .note}
48+
4349
## Parameters
4450

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

0 commit comments

Comments
 (0)