Added fallback for MAXSEARCHRESULTS in RedisMemory:GetListAsync #1063
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
Azure Redis Enterprise does not support FT.CONFIG commands which causes the method to fail completely and as this is used when deleting a document it prevents a document from being deleted.
@microsoft-github-policy-service agree |
…lback-for-maxsearchresults
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.
Motivation and Context (Why the change? What's the scenario?)
Azure Redis Enterprise does not support FT.CONFIG commands which causes the method to fail completely and as this is used when deleting a document it prevents a document from being deleted.
High level description (Approach, Design)
Added a fallback value as well as moved the configuration task into the if statement.