-
Notifications
You must be signed in to change notification settings - Fork 24.9k
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.
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
Use ValueFetcher when loading text snippets to highlight (#63572) #65441
Changes from 2 commits
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
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]] | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. breaking_710_search_changes -> breaking_711_search_changes |
||
=== Search changes | ||
|
||
[[highlight-normalization]] | ||
.Keyword fields with a custom normalizer will use the normalized form when highlighting | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Should we mention the change to |
||
[%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. | ||
==== |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
breaking_710_blah_changes -> breaking_711_blah_changes