forked from elastic/elasticsearch
-
Notifications
You must be signed in to change notification settings - Fork 3
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Use ValueFetcher when loading text snippets to highlight (elastic#63572)
HighlighterUtils.loadFieldValues() loads values directly from the source, and then callers have to deal with filtering out values that would have been removed by an ignore_above filter on keyword fields. Instead, we can use the ValueFetcher for the relevant field, which handles all this logic for us. Closes elastic#59931.
- Loading branch information
1 parent
65293df
commit f5e92be
Showing
9 changed files
with
81 additions
and
44 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,34 @@ | ||
[[breaking-changes-7.11]] | ||
== Breaking changes in 7.11 | ||
++++ | ||
<titleabbrev>7.11</titleabbrev> | ||
++++ | ||
|
||
This section discusses the changes that you need to be aware of when migrating | ||
your application to {es} 7.11. | ||
|
||
See also <<release-highlights>> and <<es-release-notes>>. | ||
|
||
// * <<breaking_710_blah_changes>> | ||
// * <<breaking_710_blah_changes>> | ||
|
||
//NOTE: The notable-breaking-changes tagged regions are re-used in the | ||
//Installation and Upgrade Guide | ||
|
||
//tag::notable-breaking-changes[] | ||
|
||
[discrete] | ||
[[breaking_710_search_changes]] | ||
=== Search changes | ||
|
||
[[highlight-normalization]] | ||
.Keyword fields with a custom normalizer will use the normalized form when highlighting | ||
[%collapsible] | ||
==== | ||
*Details* + | ||
Highlighters now use the same framework to load their values as the | ||
`fields` section of a search response. This means that normalization | ||
will be applied to the values of a keyword field; for example, a | ||
field configured with a lowercase normalizer will return highlighted | ||
snippets in lower case. | ||
==== |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters