[
https://issues.apache.org/jira/browse/IGNITE-9320?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16596129#comment-16596129
]
Vladimir Ozerov commented on IGNITE-9320:
-----------------------------------------
Additional considerations:
1) Add new atomicity mode
2) Do not allow LOCAL caches to be snapshot-based (created separate tickets to
support them in future)
3) JdbcRequestHandler/OdbcRequestHandler - now we will have to start workers
always. Let's create a ticket to optimize it in future.
4) IgniteH2Indexing - need to rework "MvccUtils.mvccEnabled" calls. Currently
we determine whether MVCC is involved before parsing. Need to do that after
parsing.
5) MvccProcessorImpl - start always, remove attribute, remove validation
6) Do not allow mixed operations between different cache types - do we have
tests?
> 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
> 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)
