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

Posted to issues@geode.apache.org by "Eric Zoerner (Jira)" <ji...@apache.org> on 2021/10/07 16:42:00 UTC

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

     [ https://issues.apache.org/jira/browse/GEODE-8840?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Eric Zoerner resolved GEODE-8840.
---------------------------------
    Fix Version/s: 1.15.0
       Resolution: Fixed

> 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
>             Fix For: 1.15.0
>
>
> 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)