You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ignite.apache.org by "Alexey Kuznetsov (JIRA)" <ji...@apache.org> on 2018/03/05 12:12:00 UTC
[jira] [Comment Edited] (IGNITE-6083) Null value have appear in the
entry processor, but the entry is existing
[ https://issues.apache.org/jira/browse/IGNITE-6083?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16383752#comment-16383752 ]
Alexey Kuznetsov edited comment on IGNITE-6083 at 3/5/18 12:11 PM:
-------------------------------------------------------------------
[~agoncharuk] Hi!
I've fixed test, checked failed tests in TC run and now its ok, plz review it : [new TC run|https://ci.ignite.apache.org/viewLog.html?buildId=1125362&tab=buildResultsDiv&buildTypeId=IgniteTests24Java8_RunAll]
was (Author: alexey kuznetsov):
[~agoncharuk] Hi!
I've fixed test, checked failed tests in TC run and now its ok, plz review it : [new TC run|https://ci.ignite.apache.org/viewQueued.html?itemId=1118525&tab=queuedBuildOverviewTab]
> 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)