ignite-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Vladimir Ozerov (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (IGNITE-9320) MVCC: finalize configuration
Date Thu, 13 Sep 2018 08:23:00 GMT

    [ https://issues.apache.org/jira/browse/IGNITE-9320?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16613186#comment-16613186

Vladimir Ozerov commented on IGNITE-9320:

[~rkondakov] my comments:
 # UpdatePlanBuilder, IgniteH2Indexing.processCaches - let's simplify error message and add
cache name and modes there. E.g. "Caches with different atomicity modes cannot participate
in the same transaction [curMode=?, problemCacheName=? problemCacheMode=?]"
 # New TODOs - please add short explanation what should be done in these specific code pieces.
Ticket number is not enough.
 # Please re-run new MVCC suites on public TC to confirm that everything is fine.

> MVCC: finalize configuration
> ----------------------------
>                 Key: IGNITE-9320
>                 URL: https://issues.apache.org/jira/browse/IGNITE-9320
>             Project: Ignite
>          Issue Type: Task
>          Components: mvcc
>            Reporter: Vladimir Ozerov
>            Assignee: Roman Kondakov
>            Priority: Major
>             Fix For: 2.7
> We need to find a way to configure MVCC caches. Currently this is a global setting, which
is not very convenient. Proposed solution:
>  # Introduce new {{CacheAtomicityMode.TRANSACTIONAL_SNAPSHOT}}
>  # Do not allow to change cache this mode during restart (when persistence is enabled)
>  # Do not allow transactions between {{TRANSACTIONAL}} and {{TRANSACTIONAL_SNAPSHOT}} caches
>  # Add limitation to cache group - all caches within a group should have the same mode

This message was sent by Atlassian JIRA

View raw message