-
Notifications
You must be signed in to change notification settings - Fork 25.5k
FieldData to use LongValues in place of NumericDocValues #136469
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
FieldData to use LongValues in place of NumericDocValues #136469
Conversation
…Values We don't need doc-by-doc iteration in FieldData, so this simplifies several implementations and also doesn't make unimplemented APIs available.
…Values We don't need doc-by-doc iteration in FieldData, so this simplifies several implementations and also doesn't make unimplemented APIs available.
Pinging @elastic/es-analytical-engine (Team:Analytics) |
Pinging @elastic/es-storage-engine (Team:StorageEngine) |
This is quite a big PR, but the vast majority of it is mechanical replacement of NumericDocValues with LongValues, and SortedNumericDocValues with SortedNumericLongValues. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM 👍
One nit, maybe seal all concrete subclasses of LongValues
and SortingNumericLongValues
?
We don't use doc-by-doc iteration in FieldData, so this simplifies several
implementations and also doesn't make unimplemented APIs available.
Adds a new SortedNumericLongValues class, analogous to
SortedNumericDoubleValues, which offers a multi-valued version of
LongValues.