-
Notifications
You must be signed in to change notification settings - Fork 793
fix(index): rebind vector readers to current object store #7944
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
Merged
wjones127
merged 2 commits into
lance-format:main
from
u70b3:fix-vector-index-cache-credential-rotation
Jul 30, 2026
+591
−112
Merged
Changes from all commits
Commits
Show all changes
2 commits
Select commit
Hold shift + click to select a range
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
Oops, something went wrong.
Oops, something went wrong.
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.
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.
issue(blocking): Legacy (v0.1/v0.2) live vector indices no longer get any in-memory index-object cache (the old
elsebranch insertingCachedLegacyVectorIndexis gone) — every query on an old-format index now reopens and reconstructs the full index each time. That's the correct fix for the credential-staleness bug, but for high-QPS users still on pre-v2 index files this could be a real latency/IO regression.TBH the stale credentials thing seems to me to be an edge case. (Most users I know that have long-lived processes configure a CredentialsProvider that can do the refresh internally.) I lean towards still having that bug for old indices than dropping support for index caching on them. What do you think about that?
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.
Agreed — restored the in-memory cache for legacy (v0.1/v0.2) live indices, so their caching behavior is unchanged from before this PR. The staleness caveat is now documented on the cache key: legacy entries assume credentials that refresh internally (e.g. a credentials provider); deployments passing fresh static credentials per dataset open should use v0.3+ index formats.
One clarification for the record: even with the legacy index-object cache removed, partition data stayed cached (the store-free partition entries), so the per-query cost was a few metadata reads rather than a full index rebuild. Either way, keeping the legacy cache is the better trade — thanks for the pushback.
The A → B → A rotation test now pins the version-specific behavior: V3 readers rebind to the current store, while a cached legacy index keeps reading through its original store.