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 GitHub Bot (Jira)" <ji...@apache.org> on 2021/02/24 22:53:00 UTC

[jira] [Commented] (GEODE-8964) Entry created via putIfAbsent with null value can write incorrect data to cache

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

ASF GitHub Bot commented on GEODE-8964:
---------------------------------------

luissson closed pull request #6046:
URL: https://github.com/apache/geode/pull/6046


   


----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

For queries about this service, please contact Infrastructure at:
users@infra.apache.org


> Entry created via putIfAbsent with null value can write incorrect data to cache
> -------------------------------------------------------------------------------
>
>                 Key: GEODE-8964
>                 URL: https://issues.apache.org/jira/browse/GEODE-8964
>             Project: Geode
>          Issue Type: Bug
>          Components: client/server
>    Affects Versions: 1.10.0, 1.14.0
>            Reporter: Louis R. Jacome
>            Assignee: Louis R. Jacome
>            Priority: Major
>             Fix For: 1.15.0
>
>
> In backwards compatibility testing, an error was seen wherein a putIfAbsent with a null value was being processed by a server but interrupted by a GII with the same key. The operation was subsequently enqueued in the client's HA Region Queue as an update with a null value rather than a create with a null value -- a path that's not supported -- resulting in erroneous data sometimes being written to the client cache.



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