[
https://issues.apache.org/jira/browse/IGNITE-2845?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15875630#comment-15875630
]
ASF GitHub Bot commented on IGNITE-2845:
----------------------------------------
GitHub user voipp opened a pull request:
https://github.com/apache/ignite/pull/1557
IGNITE-2845 Get operation might ignore entry update from EntryProcessor.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/voipp/ignite IGNITE-2845
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/ignite/pull/1557.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 #1557
----
commit e27b838b0d90dfc8479af56b7a315d84f2b684e2
Author: voipp <[email protected]>
Date: 2017-02-20T14:15:10Z
IGNITE-2845 Get operation might ignore entry update from EntryProcessor.
----
> Get operation might ignore entry update from EntryProcessor.
> ------------------------------------------------------------
>
> Key: IGNITE-2845
> URL: https://issues.apache.org/jira/browse/IGNITE-2845
> Project: Ignite
> Issue Type: Bug
> Components: cache
> Affects Versions: 1.5.0.final
> Reporter: Vladimir Ozerov
> Assignee: Alexey Kuznetsov
> Fix For: 2.0
>
>
> Originally issue was observed during work with IGFS. Steps to reproduce:
> 1) Start REPLICATE cache.
> 2) Start PESSIMISITC/REPEATABLE_READ transaction.
> 3) Invoke EntryProcessor on non-existent key and call
> "MutableEntry.setValue()" inside it.
> 4) Call {{IgniteCache.get()}} on this value. It will return {{null}}, while
> normally it should return value set inside EntryProcessor.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
