-
Notifications
You must be signed in to change notification settings - Fork 175
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
Add caching ObjectStore implementation #590
Closed
Closed
Conversation
This file contains 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
passaro
temporarily deployed
to
PR integration tests
October 31, 2023 15:17 — with
GitHub Actions
Inactive
passaro
temporarily deployed
to
PR integration tests
October 31, 2023 15:17 — with
GitHub Actions
Inactive
passaro
temporarily deployed
to
PR integration tests
October 31, 2023 15:17 — with
GitHub Actions
Inactive
passaro
temporarily deployed
to
PR integration tests
October 31, 2023 15:17 — with
GitHub Actions
Inactive
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.
Just a quick high-level pass, will try to get more detailed tomorrow. In particular, I haven't read cached_feed.rs
yet. The general approach seems right to me though.
dannycjones
reviewed
Nov 1, 2023
Introduce a new `ObjectStore` trait that replaces `ObjectClient` in the mountpoint-s3 crate. In addition to most of `ObjectClient` methods, `ObjectStore` also declares a new `prefetch` method returning a `PrefetchGetObject` which allows callers to read the object content. `PrefetchGetObject` is where `ObjectStore` implementations can add object data caching. This change also reworks the `Prefetcher` so that `ObjectStore` implementations can delegate `prefetch` to it. The main changes to `Prefetcher` are: * it is now generic on the `ObjectPartStream` (previously `ObjectPartFeed`), rather than using dynamic dispatch. * the logic to spawn a new task for each `GetObject` request and handle the object body parts returned was moved into `ObjectPartStream`. Signed-off-by: Alessandro Passaro <[email protected]>
passaro
force-pushed
the
object-store-cache
branch
from
November 1, 2023 16:39
70a1106
to
e098a01
Compare
passaro
had a problem deploying
to
PR integration tests
November 1, 2023 16:39 — with
GitHub Actions
Failure
passaro
had a problem deploying
to
PR integration tests
November 1, 2023 16:39 — with
GitHub Actions
Failure
passaro
had a problem deploying
to
PR integration tests
November 1, 2023 16:39 — with
GitHub Actions
Failure
passaro
had a problem deploying
to
PR integration tests
November 1, 2023 16:39 — with
GitHub Actions
Failure
passaro
changed the title
Introduce ObjectStore trait and add caching implementation
Add caching ObjectStore implementation
Nov 1, 2023
Signed-off-by: Alessandro Passaro <[email protected]>
Signed-off-by: Alessandro Passaro <[email protected]>
Signed-off-by: Alessandro Passaro <[email protected]>
passaro
force-pushed
the
object-store-cache
branch
from
November 2, 2023 11:52
e098a01
to
1af9bf3
Compare
passaro
had a problem deploying
to
PR integration tests
November 2, 2023 11:52 — with
GitHub Actions
Failure
passaro
had a problem deploying
to
PR integration tests
November 2, 2023 11:52 — with
GitHub Actions
Failure
passaro
had a problem deploying
to
PR integration tests
November 2, 2023 11:52 — with
GitHub Actions
Failure
passaro
had a problem deploying
to
PR integration tests
November 2, 2023 11:52 — with
GitHub Actions
Failure
Signed-off-by: Alessandro Passaro <[email protected]>
passaro
had a problem deploying
to
PR integration tests
November 2, 2023 15:50 — with
GitHub Actions
Failure
passaro
had a problem deploying
to
PR integration tests
November 2, 2023 15:50 — with
GitHub Actions
Failure
passaro
had a problem deploying
to
PR integration tests
November 2, 2023 15:50 — with
GitHub Actions
Failure
passaro
had a problem deploying
to
PR integration tests
November 2, 2023 15:50 — with
GitHub Actions
Failure
Replaced by #598 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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 of change
EDIT: This is now the follow-up to #592 which introduces a caching store implementation.
Still a draft PR to preview the use of the cache:
InMemoryCache
, which will be eventually replaced by a disk implementation,Relevant issues: #255
Does this change impact existing behavior?
No. All changes hidden under
caching
flag.By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license and I agree to the terms of the Developer Certificate of Origin (DCO).