Expose max_determinized_states in regexp query, filter
#8384
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
Contributor
|
I'd rather want this to go into 1.x for now and if we happen to update to |
Contributor
Author
|
@s1monw OK I'll switch to master only for now. |
clintongormley
changed the title
clintongormley
changed the title
clintongormley
changed the title
max_determinized_states in regexp query, filter
clintongormley
added
:Search/Search
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 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.
This PR applies to 1.4.x, and it includes a Lucene snapshot upgrade (so we can't release 1.4.1 until Lucene also releases 4.10.3).
I just plumbed the max_determinized_states through to regexp query, filter and query_string, leaving the default at Lucene's default (10000 states).
Closes #8357