Options for more flexibility for clients #128
Open
+288
−30
Conversation
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
aarshkshah1992
changed the base branch from
master
to
feat/LRU-Garbage-Collection
aarshkshah1992
changed the title
aarshkshah1992
changed the title
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.
Now that we have automated GC of transients, we need a way for callers to acquire shards with a "GetIfExists" semantics. This enables callers who do not want to pay the cost of downloading the transient to fetch a transient only if it already exists and are okay with erroring out the Acquire if the transient does not already exist.
Dagstore.Start(ctx) should respect the given context.
Config option to allow clients to specify that shards that were initialising on the previous run can be initialised on the next acquire instead of it always happening eagerly.