Skip to content
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

Add one IT for binary vector support #1527

Merged
merged 3 commits into from
Oct 11, 2024

Conversation

Hazel-Datastax
Copy link
Contributor

What this PR does:
In the previous PR #1506, one suggestion was verifying whether the decoded vector dimension matched the vector definition. I thought we needed to explicitly verify it somewhere in the code but was not sure where was the best place. So I merged that PR first and tried to figure it out later. Then I realized we can defer the vector dimension verification to DB - the same as the normal vector array value.

So I don't add any code but add one Integration test to make sure it works.

Which issue(s) this PR fixes:
Fixes #1494

Checklist

  • Changes manually tested
  • Automated Tests added/updated
  • Documentation added/updated
  • CLA Signed: DataStax CLA

@Hazel-Datastax Hazel-Datastax requested a review from a team as a code owner October 10, 2024 18:21
Copy link
Contributor

@tatu-at-datastax tatu-at-datastax left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM: just one minor naming suggestion

@Hazel-Datastax Hazel-Datastax merged commit b7a20de into main Oct 11, 2024
3 checks passed
@Hazel-Datastax Hazel-Datastax deleted the hazel/binary_vector_verification branch October 11, 2024 15:59
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Support binary vectors for Collections
2 participants