You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@geode.apache.org by "Owen Nichols (Jira)" <ji...@apache.org> on 2022/06/22 20:47:03 UTC
[jira] [Closed] (GEODE-8964) Entry created via TX 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:all-tabpanel ]
Owen Nichols closed GEODE-8964.
-------------------------------
> Entry created via TX 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
> Labels: pull-request-available
> 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.20.7#820007)