feat(storage): define vector index metadata #21885
Open
+590
−94
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.
I hereby agree to the terms of the RisingWave Labs, Inc. Contributor License Agreement.
What's changed and what's your intention?
In this PR, we define the vector index metadata in hummock. The vector index will have a separate map field in
HummockVersion
, keyed by thetable_id
of the vector index. We also define theVectorIndexDelta
inHummockVersionDelta
to represent the changes to apply on the vector index.VectorIndexDelta
can be eitherInit
orAdds
.Init
consists of the initial config of the vector index, whileAdds
consists of the data later added by the vector index writer.The GC and time travel logic is also updated, so that the vector index files can be tracked and properly GCed, and we can reuse the time travel mechanism of LSM for vector index.
Checklist
Documentation
Release note