Feature/7786 use double quote search#262
Merged
utas-raymondng merged 4 commits intomainfrom Apr 14, 2026
Merged
Conversation
utas-raymondng
requested changes
Apr 13, 2026
| should.add(CQLFields.description.getPropertyEqualToQuery(term)); // match term in original description text | ||
| } | ||
| else { | ||
| should.add(CQLFields.fuzzy_title.getPropertyEqualToQuery(t)); |
Collaborator
There was a problem hiding this comment.
Is that we just need to handle title and description only, the other field keep it as is?
Contributor
Author
There was a problem hiding this comment.
In this query, it equals:
"should":[{"match_phrase":{"title":{"query":"ARGOS"}}},{"match_phrase":{"description":{"query":"ARGOS"}}}]
So it only handle title and description with no fuzzy match. Do you think we should also include the other fields (like parameter_vocabs, id, etc.) in the exact match search?
Collaborator
There was a problem hiding this comment.
I suspect it is only the fuzzy that causing problem
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
2 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.
Currently, if we search with text, it executes a fuzzy match, so if search with
ARGOS, argo comes as well. This is not expected according to user feedback:So allow exact search with term if user type text with double quote:
Query:
[DEV] 2026-04-13 16:55:20 DEBUG ElasticSearchBase:373 - Elastic search payload for count CountRequest: POST /es-indexer-edge/_count {"query":{"script_score":{"query":{"bool":{"filter":[{"geo_bounding_box":{"summaries.proj:geometry":{"top_left":{"lat":-8.0,"lon":104.0},"bottom_right":{"lat":-43.0,"lon":163.0}}}}],"minimum_should_match":"1","must":[{"match_all":{}}],"should":[{"match_phrase":{"title":{"query":"ARGOS"}}},{"match_phrase":{"description":{"query":"ARGOS"}}}]}},"script":{"source":"double internalScore = doc.containsKey('summaries.score') && !doc['summaries.score'].empty ? doc['summaries.score'].value : 0.0; double normalizedScore = internalScore / 106.0; double multiplier = Math.max(normalizedScore, 0.01); return _score * multiplier;","lang":"painless"}}}}