Skip to content

CNDB-15701: Forbid creating vector indexes if version is earlier than CA #2090

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.

Sign up for GitHub

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

Jump to bottom
Draft
wants to merge 1 commit into
base: main-5.0
Choose a base branch
from
Draft

CNDB-15701: Forbid creating vector indexes if version is earlier than CA #2090

wants to merge 1 commit into from

Conversation

@michaelsembwever
Copy link
Member

@michaelsembwever michaelsembwever commented Oct 28, 2025

https://github.com/riptano/cndb/issues/15751

Port into main-5.0 commit 945b7a1

CNDB-15751: CNDB-15701: Forbid creating vector indexes if version is earlier than CA (#2071)

Creating vector indexes if version is earlier than CA would usually fail in the asynchronous build. This patch makes them fail synchronously at CREATE INDEX depending on the local index version. If the local node has the right version but any of the remotes doesn't, the failure will remain asynchronous.

BLOCKED on #2080 (for VersionSelectorTest.java)

@adelapena @michaelsembwever
CNDB-15751: CNDB-15701: Forbid creating vector indexes if version is …
32927fe 
…earlier than CA (#2071)

Creating vector indexes if version is earlier than CA would usually fail in the asynchronous build.
This patch makes them fail synchronously at CREATE INDEX depending on the local index version.
If the local node has the right version but any of the remotes doesn't, the failure will remain
asynchronous.
@github-actions
Copy link

github-actions bot commented Oct 28, 2025

Checklist before you submit for review

  • This PR adheres to the Definition of Done
  • Make sure there is a PR in the CNDB project updating the Converged Cassandra version
  • Use NoSpamLogger for log lines that may appear frequently in the logs
  • Verify test results on Butler
  • Test coverage for new/modified code is > 80%
  • Proper code formatting
  • Proper title for each commit staring with the project-issue number, like CNDB-1234
  • Each commit has a meaningful description
  • Each commit is not very long and contains related changes
  • Renames, moves and reformatting are in distinct commits
  • All new files should contain the DataStax copyright header instead of the Apache License one

@michaelsembwever michaelsembwever mentioned this pull request Oct 28, 2025
Open
@djatnieks
Copy link

djatnieks commented Nov 4, 2025

#2080 is approved now - this one is still marked as Draft

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

No reviews

Assignees

No one assigned

Labels

None yet

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

4 participants

@michaelsembwever @djatnieks @adelapena