RS and RC: Client-side caching and compatibility #550
Merged
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
…ax_keys_policy to REST API and rladmin for client-side caching
…compatibility reference
andy-stark-redis
approved these changes
Aug 15, 2024
content/operate/rs/references/compatibility/client-side-caching.md
Outdated
Show resolved
Hide resolved
Co-authored-by: andy-stark-redis <164213578+andy-stark-redis@users.noreply.github.com>
|
Looks good to me. What happens if tracking-table-max-keys is exceeded? @yoavredis |
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.
DOC-3951
Please note that some of the relrefs that point to client-side caching devex docs will not work until Andy's PR #530 is merged or cherry-picked to this branch. I thought it might be easier to review the Enterprise-specific changes if I waited to pull in Andy's changes.