Add TTL-based snapshot caching for DuckLake catalog #2
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.
Summary
Adds configurable time-to-live (TTL) based caching for snapshot resolution in
DuckLakeCatalog, allowing users to balance data freshness against query performance.Changes
SnapshotConfigstruct withttl_seconds: Option<u64>fieldDuckLakeCatalog::new_with_config()for custom snapshot configurationTTL = 0(default): Always query latest snapshotTTL > 0: Cache snapshot for specified durationTTL = None: Cache snapshot foreverRwLockwith double-check lockingAPI