feat(cache): add generic cache trait for different object reader #9436
+710
−0
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 CLA available at: https://databend.rs/dev/policies/cla/
Summary
Goal
The goal is for each object cache provider to be more flexible and able to define its cache policy:
Usage
Usage(MemoryItemsCache):
Usage(ByPassCache = No cache, same as object operations via CachedObjectAccessor):
Notes
This is the first part. We implement three cache backends:
Next PR will try to replace the following:
SegmentInfoCache/TableSnapshotCache/TableSnapshotStatisticCache/BloomIndexCache/BloomIndexMetaCache/FileMetaDataCache
to the new.Closes #issue