Handle unsigned long in search operations in star tree #1
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.
Description
Parent issue - [Star tree] Handle 'unsigned long' as part of star tree #15231
Handle unsigned long in search operations in star tree.
We are now using Long.ParseUnsignedLong() to parse unsigned-long values in the query side.
Related Issues
[Star tree] Handle 'unsigned long' as part of star tree #15231
[Star Tree ] Handle unsigned long during flush and merge operations #16645
This PR along with Indexing PR together resolves opensearch-project#15231
Check List
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.
For more information on following Developer Certificate of Origin and signing off your commits, please check here.