[
https://issues.apache.org/jira/browse/IGNITE-6416?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16237333#comment-16237333
]
Vladimir Ozerov commented on IGNITE-6416:
-----------------------------------------
[~al.psc], the following tests start failing:
DynamicColumnsConcurrentAtomicPartitionedSelfTest.testConcurrentRebalance
DynamicColumnsConcurrentAtomicPartitionedSelfTest.testCoordinatorChange
DynamicColumnsConcurrentAtomicReplicatedSelfTest.testConcurrentRebalance
DynamicColumnsConcurrentAtomicReplicatedSelfTest.testCoordinatorChange
DynamicColumnsConcurrentTransactionalPartitionedSelfTest.testConcurrentRebalance
DynamicColumnsConcurrentTransactionalPartitionedSelfTest.testCoordinatorChange
DynamicColumnsConcurrentTransactionalReplicatedSelfTest.testConcurrentRebalance
DynamicColumnsConcurrentTransactionalReplicatedSelfTest.testCoordinatorChange
> SQL: DDL tests should not check internal structures, but rather rely on
> expected public behavior
> ------------------------------------------------------------------------------------------------
>
> Key: IGNITE-6416
> URL: https://issues.apache.org/jira/browse/IGNITE-6416
> Project: Ignite
> Issue Type: Task
> Components: sql
> Affects Versions: 2.3
> Reporter: Vladimir Ozerov
> Assignee: Alexander Paschenko
> Priority: Major
> Fix For: 2.4
>
>
> We need to review our DDL tests. Looks like there are a lot waits in the
> tests which mask concurrency bugs (e.g. see IGNITE-6403). Instead, we should
> do the following:
> 1) If we want to tests asynchronous propagation of changes to clients,
> separate test should be created for this
> 2) For all other cases we should not use private API at all, and do not
> perform any waits.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
