Make optimizedText wrapper aware #132461
Merged
Make optimizedText wrapper aware #132461
Conversation
This file contains hidden or 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
felixbarny
added
>non-issue
:Core/Infra/Core
elasticsearchmachine
added
Team:Core/Infra
|
Pinging @elastic/es-storage-engine (Team:StorageEngine) |
elasticsearchmachine
added
v9.2.0
external-contributor
|
Pinging @elastic/es-core-infra (Team:Core/Infra) |
|
@elasticmachine test this please |
|
Oops sorry, just realized CI had already run. I saw the |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
4 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Before this change,
IndexRoutingwasn't able to fully take advantage ofoptimizedText. That's because it is using a non defaultXContentParserConfiguration(withFiltering), which creates a wrapper (FilteringParserDelegate). This prevented the parser to access theESUTF8StreamJsonParser.