[Star Tree ] Handle unsigned long during flush and merge operations #16645
Labels
enhancement
Enhancement or improvement to existing feature or request
Indexing
Indexing, Bulk Indexing and anything related to indexing
untriaged
Comments
Shailesh-Kumar-Singh
added
enhancement
github-actions
bot
added
the
Indexing
3 tasks
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Is your feature request related to a problem? Please describe
Parent issue - [Star tree] Handle 'unsigned long' as part of star tree #15231
During flush and merge operations, unsigned long values in number fields are stored as Java.Long. When the unsigned long exceeds Long.MAX_VALUE, the value becomes negative, causing issues with comparison.
Describe the solution you'd like
Numeric dimensions now include an
isUnsignedLongflag to indicate whether the value is unsigned, which impacts sorting and comparison operations. During sorting,Long.compareUnsignedis used to handle unsigned long values, ensuring that they are correctly compared even when they exceed the maximum value of a signed long.Related component
Indexing
Describe alternatives you've considered
No response
Additional context
No response
The text was updated successfully, but these errors were encountered: