You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ignite.apache.org by "ASF GitHub Bot (JIRA)" <ji...@apache.org> on 2017/09/15 17:06:00 UTC
[jira] [Commented] (IGNITE-2845) Get operation might ignore entry
update from EntryProcessor.
[ https://issues.apache.org/jira/browse/IGNITE-2845?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16168191#comment-16168191 ]
ASF GitHub Bot commented on IGNITE-2845:
----------------------------------------
Github user voipp closed the pull request at:
https://github.com/apache/ignite/pull/1557
> 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: Alexandr Fedotov
> Fix For: 2.3
>
>
> 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.4.14#64029)