[
https://issues.apache.org/jira/browse/IGNITE-6083?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16370202#comment-16370202
]
ASF GitHub Bot commented on IGNITE-6083:
----------------------------------------
GitHub user voipp opened a pull request:
https://github.com/apache/ignite/pull/3546
IGNITE-6083 alternate fix version
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/voipp/ignite ignite-6083-2
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/ignite/pull/3546.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #3546
----
commit 236b63bb7f3ebd214a690b168edf14c6c1832c95
Author: voipp <alkuznetsov.sb@...>
Date: 2018-02-20T16:09:12Z
IGNITE-6083 alternate fix version
----
> Null value have appear in the entry processor, but the entry is existing
> ------------------------------------------------------------------------
>
> Key: IGNITE-6083
> URL: https://issues.apache.org/jira/browse/IGNITE-6083
> Project: Ignite
> Issue Type: Bug
> Components: cache
> Affects Versions: 2.1
> Reporter: Vladislav Pyatkov
> Assignee: Alexey Kuznetsov
> Priority: Major
> Attachments: EntryProcessorInOptimisticTxTest.java
>
>
> In one thread load some data in a cache, after that I have execute
> OPTIMISTIC, SERIALIZABLE transaction with two {{IgniteCache.invoke()}}
> methods.
> The value had been corrected at first {{EntryProcessor}}, but it is NULL at
> second.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
