[
https://issues.apache.org/jira/browse/GEODE-8386?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17168962#comment-17168962
]
ASF subversion and git services commented on GEODE-8386:
--------------------------------------------------------
Commit 42c086b6578b6f0f768a3ff9ead627fbe70abf22 in geode's branch
refs/heads/develop from Darrel Schneider
[ https://gitbox.apache.org/repos/asf?p=geode.git;h=42c086b ]
GEODE-8386: fix SRANDMEMBER with negative count (#5404)
> SRANDMEMBER with negative count should return that many members
> ---------------------------------------------------------------
>
> Key: GEODE-8386
> URL: https://issues.apache.org/jira/browse/GEODE-8386
> Project: Geode
> Issue Type: Bug
> Components: redis
> Reporter: Darrel Schneider
> Assignee: Darrel Schneider
> Priority: Major
> Labels: pull-request-available
> Fix For: 1.14.0
>
>
> When SRANDMEMBER is sent a negative count, it should return a number of items
> equal to the absolute value. uniqueness is not guaranteed.
>
> {{SADD abc 123 456
> SRANDMEMBER abc -1 -> 123
> SRANDMEMBER abc -2 -> 123, 123 OR 123, 456, 456, 123 OR 456, 456
> SRANDMEMBER abc -5 -> 123,123,456,123,456 OR any one of the 2^5
> combinations...}}
> see the redis unit tests and docs: unit/type/set -> SRANDMEMBER with <count>
> - hashtable
> and documentation: [https://redis.io/commands/srandmember]
> Currently, Geode Redis returns only up to as many members as there are in the
> set.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
