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.
Make sure that:
mvn formatter:format
target. Don’t submit any formatting related changes.DOC-4757
Couple of things to note:
exceptionally()
in the rule_1.1 example to handle the exception that it demonstrates. Is this best approach? There seem to be a few ways to handle exceptions withCompletableFuture
.del()
commands at the start of some of the examples because they are hidden in the examples for the other clients/languages. However, would it be better to actually show thedel()
calls for Lettuce, given that theCompletableFuture
instances are chained together? In some examples, the first line basically tells you the name of the previous example in the chain, so would readers assume that the new example starts with the same DB state that the previous one ended with?