[
https://issues.apache.org/jira/browse/GEODE-8964?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17290525#comment-17290525
]
ASF GitHub Bot commented on GEODE-8964:
---------------------------------------
luissson opened a new pull request #6053:
URL: https://github.com/apache/geode/pull/6053
…e incorrect data to cache (#6046)
- Modifies TXCommitMessage.firePendingCallbacks to check if an Entry
Event is an Update with a null value, if so callbacks are invoked using
an AFTER_CREATE and not AFTER_UPDATE. This handles a situation that
can occur when a transactional create with null value is interrupted by a
GII on the
same key, resulting in a AFTER_UPDATE event being distributed instead of a
AFTER_CREATE.
Thank you for submitting a contribution to Apache Geode.
In order to streamline the review of the contribution we ask you
to ensure the following steps have been taken:
### For all changes:
- [ ] Is there a JIRA ticket associated with this PR? Is it referenced in
the commit message?
- [ ] Has your PR been rebased against the latest commit within the target
branch (typically `develop`)?
- [ ] Is your initial contribution a single, squashed commit?
- [ ] Does `gradlew build` run cleanly?
- [ ] Have you written or updated unit tests to verify your changes?
- [ ] If adding new dependencies to the code, are these dependencies
licensed in a way that is compatible for inclusion under [ASF
2.0](http://www.apache.org/legal/resolved.html#category-a)?
### Note:
Please ensure that once the PR is submitted, check Concourse for build
issues and
submit an update to your PR as soon as possible. If you need help, please
send an
email to [email protected].
----------------------------------------------------------------
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:
[email protected]
> 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
> 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.3.4#803005)