Allow opting out of known Lucene file extensions check #74316
Merged
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
ywelsch
added
>non-issue
:Search/Search
|
Pinging @elastic/es-search (Team:Search) |
ywelsch
added a commit
that referenced
this pull request
Jun 21, 2021
Allows plugin developers of custom codecs to opt out of the assertion in LuceneFilesExtensionsTests that checks that all encountered Lucene file extensions are known to this class. In the future, we would like to add a proper plugin extension point for this. Relates #74150
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Allows plugin developers of custom codecs to opt out of the assertion in LuceneFilesExtensionsTests that checks that all encountered Lucene file extensions are known to this class. In the future, we would like to add a proper plugin extension point for this.
Relates #74150