You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ignite.apache.org by "Ignite TC Bot (JIRA)" <ji...@apache.org> on 2019/03/22 21:33:00 UTC
[jira] [Commented] (IGNITE-11587) MVCC: Remote tx determine its
type in wrong way.
[ https://issues.apache.org/jira/browse/IGNITE-11587?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16799372#comment-16799372 ]
Ignite TC Bot commented on IGNITE-11587:
----------------------------------------
{panel:title=--> Run :: All: No blockers found!|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}{panel}
[TeamCity *--> Run :: All* Results|https://ci.ignite.apache.org/viewLog.html?buildId=3371795&buildTypeId=IgniteTests24Java8_RunAll]
> MVCC: Remote tx determine its type in wrong way.
> -------------------------------------------------
>
> Key: IGNITE-11587
> URL: https://issues.apache.org/jira/browse/IGNITE-11587
> Project: Ignite
> Issue Type: Bug
> Components: mvcc
> Reporter: Andrew Mashenkov
> Assignee: Andrew Mashenkov
> Priority: Major
> Fix For: 2.8
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> Remote tx adapters implements IgniteTxState.mvccEnabled in wrong way.
> mvccEnabled() checks if writeMap contains a mvcc-entry, but writeMap is always empty for mvcc.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)