-
Notifications
You must be signed in to change notification settings - Fork 691
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
MB-59616: Adding vector_base64 field #2012
Conversation
Likith101
commented
Apr 10, 2024
- Added a new field type called vector_base64.
- Acts similar to vector in most cases.
- When a new document arrives in the bleve layer, during the parsing of all its fields in processProperty, if the field mapping type is vector-base64, then its value is decoded into a vector field and processed like a vector.
- The standard golang base64 library is used for the decode operation.
- Added a new field type called vector_base64. - Acts similar to vector in most cases. - When a new document arrives in the bleve layer, during the parsing of all its fields in processProperty, if the field mapping type is vector-base64, then its value is decoded into a vector field and processed like a vector. - The standard golang base64 library is used for the decode operation.
- Added VectorBase64 of type string to the KNNRequest struct - ValidateKNN will handle the decoding of the encoded string and fill the vector field with the vector value
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.
@Likith101 looking mostly ready. Would you add a benchmark test to here that tests time taken for DecodeVector(..)
for a few dimensionalities - maybe 128, 784, 1536.
@Likith101 faiss_vector_base64_test.go should also get the |
@Likith101 Did you already run the decode algorithm by Jon? |
I ran the decode algorithm by Jon, so no changes necessary there. |
These are the benchmark results for the decode function done on my local system.
|