[
https://issues.apache.org/jira/browse/IGNITE-9537?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16611690#comment-16611690
]
Roman Kondakov commented on IGNITE-9537:
----------------------------------------
Tests fails caused by configuration changes:
# Platform .NET:
## Apache.Ignite.Core.Tests.exe: Apache.Ignite.Core.Tests.ApiParity
### IgniteConfigurationParityTest.TestIgniteConfiguration - global mvcc
enabled flag has been removed.
## Apache.Ignite.Core.Tests.exe: Apache.Ignite.Core.Tests.Cache
### DataRegionMetricsTest.TestMemoryMetrics - txLog data region now is always
started.
### MemoryMetricsTest.TestMemoryMetrics - txLog data region now is always
started.
# Platform .NET (Core Linux)
## Apache.Ignite.Core.Tests.DotNetCore.dll: Apache.Ignite.Core.Tests.ApiParity
### IgniteConfigurationParityTest.TestIgniteConfiguration
## Apache.Ignite.Core.Tests.DotNetCore.dll: Apache.Ignite.Core.Tests.Cache
### DataRegionMetricsTest.TestMemoryMetrics
> .NET: Change MVCC enabled configuration.
> ----------------------------------------
>
> Key: IGNITE-9537
> URL: https://issues.apache.org/jira/browse/IGNITE-9537
> Project: Ignite
> Issue Type: Task
> Components: mvcc, platforms
> Reporter: Roman Kondakov
> Priority: Major
> Labels: .net
> Fix For: 2.7
>
>
> MVCC enabled configuration has changed from the node global flag to per-cache
> atomicity mode setting {{CacheAtomicityMode#TRANSACTIONAL_SNAPSHOT}}. We need
> to reflect this change in .NET API.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
