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

Maksim Davydov commented on IGNITE-28952:
-----------------------------------------

https://ci2.ignite.apache.org/buildConfiguration/IgniteTests24Java8_CheckCodeStyleDucktests?branch=pull%2F13431%2Fhead#all-projects

> [ducktests] Make the cache level topology validator optional in MDC tests
> -------------------------------------------------------------------------
>
>                 Key: IGNITE-28952
>                 URL: https://issues.apache.org/jira/browse/IGNITE-28952
>             Project: Ignite
>          Issue Type: Task
>            Reporter: Maksim Davydov
>            Assignee: Maksim Davydov
>            Priority: Minor
>              Labels: IEP-140, ducktests, ise
>
>  The MDC test applications always configure the cache with 
> MdcTopologyValidator
>   (MdcCacheAwareApplication), so the scenarios only run against a validator
>   configured per cache. 
>   The scenarios themselves are validator agnostic: the load applications 
> treat any
>   CacheException/IgniteException as a rejected write, without inspecting its 
> type.
>   Only the cache configuration is in the way.
>   Changes:
>   * MdcCacheAwareApplication: new 'topologyValidator' parameter, default 
> true. When
>     false, the cache is created without the cache level validator and the
>     mainDc/datacenters parameters are not required.
>   * MdcCluster: new 'mdc_cache_topology_validator' global (default true) 
> applied to
>     every cache the fixture creates.
>   * README: document the global.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

Reply via email to