Backport to net8 - Caching: SE.Redis update and fix naming inconsistency #54413
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
* - rev to SE.Redis 2.7.27 - use new AddLibraryNameSuffix API (2.7.27) - do not use ConfigurationOptions.Clone() - impacts key rotation - attach suffix even if ConnectionMultiplexerFactory used (Aspire)
mgravell
requested review from
BrennanConroy,
halter73,
captainsafia,
wtgodbe and
a team
as code owners
dotnet-issue-labeler
bot
added
the
area-middleware
mgravell
added
Servicing-consider
adityamandaleeka
approved these changes
Mar 7, 2024
justindbaur
reviewed
Mar 8, 2024
mgravell
added
Servicing-approved
|
approved by servicing tactics 8th /cc @wtgodbe |
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.
backport of #54239 to .NET 8
this improves visibility of cache metrics, in particular useful and relevant for #53255
(automatic backport failed; this is just
git cherry-pick 7874b36fd8da2f8e56b23aac48954f14bafba1fe- no merge conflicts found)Customer impact:
Regression?
No
Risk
Low
Routine library bump; new API usage is best-efforts only