Alter ES query exact match params for altered 'underscore search' performance #149
Conversation
This file contains 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
…E and disable ELASTICSEARCH_QUERY_EXACT_MATCH_WITH_PREFIX to achieve expected underscore search behaviour
murdo-moj
approved these changes
Jun 7, 2024
|
Going to close this as i think what Mitch has done in later releases of datahub supersede this |
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.
Underscores within exact search in DataHub don't return the expected results. A suggestion from the DataHub Slack is:
This leads to more results than expected - another response suggested:
This PR adopts those suggestions