RCBC-489: Support for base64 encoded vector types #146
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
avsej
approved these changes
May 29, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Motivation
In 7.6.2, the server will support base64 encoding of vectors in addition to array type "vector". The new encoding type will be accepted via the parameter "vector_base64" in the vector search query.
Changes
VectorQuerythat accepts a string which represents a base64 encoded sequence of little-endian IEEE 754 floats. This is then forwarded as-is in the vector search query using the"vector_base64" parameter.f72a089which includes raisingFeatureNotAvailableinSearchIndexManager#upsert_index&ScopeSearchIndexManager#upsert_indexwhen upserting indexes with vector definitions to servers that do not support it.Results
All vector search tests in FIT pass