-
Couldn't load subscription status.
- Fork 1.2k
Tidy up Lucene104ScalarQuantizedVectorsWriter #15357
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
base: main
Are you sure you want to change the base?
Conversation
|
This PR does not have an entry in lucene/CHANGES.txt. Consider adding one. If the PR doesn't need a changelog entry, then add the skip-changelog label to it and you will stop receiving this reminder on future updates to the PR. |
| */ | ||
| protected Lucene104ScalarQuantizedVectorsWriter( | ||
| /** Sole constructor */ | ||
| public Lucene104ScalarQuantizedVectorsWriter( |
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.
seems OK, but why make it public?
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.
So the writer (and so the format it represents) can be created and used by other classes outside of Lucene104ScalarQuantizedVectorsFormat. The reader is already public.
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.
ok that is kind of a tautology - I will be like the 5-year-old here and ask so why do we want the writer to be created and used by other classes outside of Lucene104ScalarQuantizedVectorsFormat :) I really have no objection - just curious what motivated this
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.
See elastic/elasticsearch#136627 (comment) - we want to use the new quantizer in some updated formats in Elasticsearch
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.
got it thanks. Would love to see the bfloat16 support contributed here at some point!
Fix up the javadocs and constructor accessibility