This repository was archived by the owner on Oct 10, 2025. It is now read-only.
Fix DROP_VECTOR_INDEX persistence bug preventing property updates #6041
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
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
1 participant
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.
Description
When dropping a vector index via
DROP_VECTOR_INDEX, the index was correctly removed from the catalog butNodeTable::dropIndex()was missinghasChanges = true. This caused the table's serialized index list to not be updated during checkpoint, leading to the dropped index persisting across database restarts.This prevented property updates on previously-indexed columns with the error
"Cannot set property ... because it is used in one or more indexes", even thoughSHOW_INDEXES()showed no indexes remaining.Fixes #6040
Contributor agreement