Add operator, boost, prefix length, and max expansions to MultiMatchQuery #71
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
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.
This PR enhances the
MultiMatchQueryclass by adding new parameters. It also introduces a comprehensive test suite for theMultiMatchQueryclass to ensure correctness and robustness, in line with the already existingMatchQueryTest.Enhancements to
MultiMatchQuery:operator,boost,prefixLength, andmaxExpansions. These parameters allow more fine-grained control over the query behavior. I do feel the arguments are getting to a point that there are too many, especially when we would add even more. Ideally, this should be approached differently, but this would require some more discussion.