[
https://issues.apache.org/jira/browse/IGNITE-9320?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16598788#comment-16598788
]
ASF GitHub Bot commented on IGNITE-9320:
----------------------------------------
GitHub user rkondakov opened a pull request:
https://github.com/apache/ignite/pull/4660
IGNITE-9320: Mvcc cache configuration and cluster nodes validation.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gridgain/apache-ignite ignite-9320
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/ignite/pull/4660.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 #4660
----
commit b00fd2a7d315e194b630f4ac2ba09842e69de48d
Author: rkondakov <kondakov87@...>
Date: 2018-08-30T09:09:59Z
IGNITE-9320: Mvcc configuration changed from global flag to per cache flag.
Tests fixed.
commit 1305e54d0afa046aa1100824b9c9a56bc5f84d7a
Author: rkondakov <kondakov87@...>
Date: 2018-08-31T11:20:15Z
Start mvcc processor and cluster validation WIP
----
> 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
(v7.6.3#76005)
