Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Consider ReadFrom.isOrderSensitive() in cluster scan command #1146

Closed
mp911de opened this issue Oct 10, 2019 · 0 comments
Closed

Consider ReadFrom.isOrderSensitive() in cluster scan command #1146

mp911de opened this issue Oct 10, 2019 · 0 comments
Labels
type: bug A general bug
Milestone
5.2.1

Comments

@mp911de
Copy link
Collaborator

mp911de commented Oct 10, 2019 •
edited
Loading

ReadFrom.isOrderSensitive() isn't considered when issuing a cluster-wide scan. Instead, the first node is used instead of randomizing the collection of nodeId's.

We should apply randomization for consistent behavior.
@mp911de mp911de added the type: bug A general bug label Oct 10, 2019
@mp911de mp911de added this to the 5.2.1 milestone Oct 16, 2019
mp911de added a commit that referenced this issue Oct 16, 2019
@mp911de
Consider ReadFrom.isOrderSensitive() in cluster scan command #1146
a8afab9 
ReadFrom order sensitivity is now considered in Cluster SCAN for keys.
mp911de added a commit that referenced this issue Oct 16, 2019
@mp911de
Consider ReadFrom.isOrderSensitive() in cluster scan command #1146
5d00a3d 
ReadFrom order sensitivity is now considered in Cluster SCAN for keys.
@mp911de mp911de closed this as completed Oct 16, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
type: bug A general bug
Projects
None yet
Milestone
5.2.1
Development

No branches or pull requests
1 participant
@mp911de