Added a HybridCachingOption to throw an error if the distributed cache throws an error #413
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
…e throws an exception
|
We will take a look ASAP. |
|
@catcherwong could I know when this feature will be coming out on a release? |
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.
Added a HybridCachingOption to throw an error if the distributed cache throws an error. Added this functionality to be able to guarantee certain changes which might happen to the distributed cache. Wondering if its okay to have something like EnsureDistributedCacheUpdates to make sure the updates are actually sent. As it currently stands there is no easy way to guarantee any updates to the distributed cache are actually written. This will be an opt-in feature without breaking any existing functionality