You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@geode.apache.org by "ASF subversion and git services (Jira)" <ji...@apache.org> on 2021/09/30 20:21:00 UTC

[jira] [Commented] (GEODE-8840) implement redis RENAMENX command

    [ https://issues.apache.org/jira/browse/GEODE-8840?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17423002#comment-17423002 ] 

ASF subversion and git services commented on GEODE-8840:
--------------------------------------------------------

Commit 3c70feeb9d0f7e9b8514ae6676ffacff8e4c358e in geode's branch refs/heads/develop from Eric Zoerner
[ https://gitbox.apache.org/repos/asf?p=geode.git;h=3c70fee ]

GEODE-8840: Support RENAMENX command (#6877)



> implement redis RENAMENX command
> --------------------------------
>
>                 Key: GEODE-8840
>                 URL: https://issues.apache.org/jira/browse/GEODE-8840
>             Project: Geode
>          Issue Type: Improvement
>          Components: redis
>            Reporter: John Hutchison
>            Assignee: Eric Zoerner
>            Priority: Major
>              Labels: pull-request-available
>
> Note: see implementation of SETNX, RENAME
> Notes relating to [the now-closed PR|[https://github.com/apache/geode/pull/5915]]: Currently there's a race condition between when the new key's existence is checked, and the old key is renamed. It's possible for two RENAMENX operations, on separate threads, renaming to the SAME new key, to BOTH succeed. At most one should succeed. The existing DUNIT test illustrates this problem.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)