-
Notifications
You must be signed in to change notification settings - Fork 21
CNDB-14343: Fix ANN queries on primary key and static columns #1800
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
Checklist before you submit for review
|
15ab387
to
43e710d
Compare
if (!column.isRegular()) | ||
return true; |
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.
I think this is only correct for Primary Key columns since those cannot be updated to a new value. Static columns can be updated and that means we need to validate their source ss/mem table.
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.
I have added a tiny test case for updating a static column similar to that of VectorUpdateDeleteTest.testUpdateVectorToWorseAndBetterPositions
. It seems to work, but it probably needs more testing.
43e710d
to
036f1bc
Compare
036f1bc
to
4fa17fb
Compare
924d122
to
251c318
Compare
eac82ce
to
b90cace
Compare
|
✔️ Build ds-cassandra-pr-gate/PR-1800 approved by ButlerApproved by Butler |
We can create a vector index on primary key components and static columns and query an empty table. Still, if an ANN query finds any data, we get an unmanaged replica-side error saying that only regular columns are supported.
For now, I'm just adding some reproduction tests here.