DATAREDIS-756 - Order results of partitioned multi-key commands by positional keys. #303
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
…ll results. Prepare issue branch.
…sitional keys. We now order and assemble results of multi-key commands (e.g. MGET with cross-slot keys) that are executed on different nodes by positional keys to retain duplicate keys in the requested order and retain the server response. Previously duplicate keys were treated as set of keys and the response didn't match the requested keys.
Visibility modifications.
christophstrobl
pushed a commit
that referenced
this pull request
Jan 23, 2018
…sitional keys. We now order and assemble results of multi-key commands (e.g. MGET with cross-slot keys) that are executed on different nodes by positional keys to retain duplicate keys in the requested order and retain the server response. Previously duplicate keys were treated as set of keys and the response didn't match the requested keys. Original Pull Request: #303
christophstrobl
added a commit
that referenced
this pull request
Jan 23, 2018
Visibility modifications. Original Pull Request: #303
christophstrobl
pushed a commit
that referenced
this pull request
Jan 23, 2018
…sitional keys. We now order and assemble results of multi-key commands (e.g. MGET with cross-slot keys) that are executed on different nodes by positional keys to retain duplicate keys in the requested order and retain the server response. Previously duplicate keys were treated as set of keys and the response didn't match the requested keys. Original Pull Request: #303
christophstrobl
added a commit
that referenced
this pull request
Jan 23, 2018
Visibility modifications. Original Pull Request: #303
christophstrobl
pushed a commit
that referenced
this pull request
Jan 23, 2018
…sitional keys. We now order and assemble results of multi-key commands (e.g. MGET with cross-slot keys) that are executed on different nodes by positional keys to retain duplicate keys in the requested order and retain the server response. Previously duplicate keys were treated as set of keys and the response didn't match the requested keys. Original Pull Request: #303
christophstrobl
added a commit
that referenced
this pull request
Jan 23, 2018
Visibility changes. Original Pull Request: #303
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.
We now order and assemble results of multi-key commands (e.g.
MGETwith cross-slot keys) that are executed on different nodes by positional keys to retain duplicate keys in the requested order and retain the server response.Previously duplicate keys were treated as a set of keys and the response didn't match the requested keys.
Related ticket: DATAREDIS-756.