[
https://issues.apache.org/jira/browse/IGNITE-11202?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16760671#comment-16760671
]
Ignite TC Bot commented on IGNITE-11202:
----------------------------------------
{panel:title=--> Run :: All: Possible
Blockers|borderStyle=dashed|borderColor=#ccc|titleBGColor=#F7D6C1}
{color:#d04437}Cache (Restarts) 1{color} [[tests
4|https://ci.ignite.apache.org/viewLog.html?buildId=3003504]]
* IgniteCacheRestartTestSuite:
GridCacheReplicatedNodeRestartSelfTest.testRestartWithPutFourNodesNoBackups -
0,0% fails in last 395 master runs.
{color:#d04437}Queries 1{color} [[tests
3|https://ci.ignite.apache.org/viewLog.html?buildId=3003535]]
* IgniteBinaryCacheQueryTestSuite:
near.IgniteCacheDistributedPartitionQueryNodeRestartsSelfTest
{color:#d04437}MVCC Queries{color} [[tests
20|https://ci.ignite.apache.org/viewLog.html?buildId=3003492]]
* IgniteCacheMvccSqlTestSuite:
CacheMvccSqlLockTimeoutTest.testLockTimeoutsAfterDefaultTxTimeoutForReplicatedCache
- 0,0% fails in last 418 master runs.
* IgniteCacheMvccSqlTestSuite:
CacheMvccTxNodeMappingTest.testAllTxNodesAreTrackedSrv - 0,0% fails in last 418
master runs.
* IgniteCacheMvccSqlTestSuite:
CacheMvccSizeTest.testDeleteChangesSizeAfterUnlock - 0,0% fails in last 418
master runs.
* IgniteCacheMvccSqlTestSuite: CacheMvccSizeTest.testSql - 0,0% fails in last
418 master runs.
* IgniteCacheMvccSqlTestSuite:
CacheMvccSqlLockTimeoutTest.testLockTimeoutsAfterDefaultTxTimeoutForPartitionedCache
- 0,0% fails in last 418 master runs.
* IgniteCacheMvccSqlTestSuite:
CacheMvccSqlLockTimeoutTest.testLockTimeoutsForPartitionedCache - 0,0% fails in
last 418 master runs.
{color:#d04437}Continuous Query 2{color} [[tests
1|https://ci.ignite.apache.org/viewLog.html?buildId=3003454]]
* IgniteCacheQuerySelfTestSuite4:
CacheContinuousQueryFailoverMvccTxSelfTest.testStartStop - 0,0% fails in last
407 master runs.
{color:#d04437}Cassandra Store{color} [[tests
1|https://ci.ignite.apache.org/viewLog.html?buildId=3003558]]
* IgniteCassandraStoreTestSuite: tests.CassandraDirectPersistenceTest
{color:#d04437}MVCC Cache 2{color} [[tests 0 TIMEOUT , Exit Code
|https://ci.ignite.apache.org/viewLog.html?buildId=3003546]]
{panel}
[TeamCity *--> Run :: All*
Results|https://ci.ignite.apache.org/viewLog.html?buildId=3003559&buildTypeId=IgniteTests24Java8_RunAll]
> SQL: Move partition reservation logic to separate class
> -------------------------------------------------------
>
> Key: IGNITE-11202
> URL: https://issues.apache.org/jira/browse/IGNITE-11202
> Project: Ignite
> Issue Type: Task
> Components: sql
> Reporter: Vladimir Ozerov
> Assignee: Vladimir Ozerov
> Priority: Major
> Fix For: 2.8
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> Currently associated logic is located inside {{GridMapQueryExecutor}}. This
> is wrong because partitions should be reserved and then released for both
> local and distributed queries. To allow for smooth merge of "map" and "local"
> queries in future, it is necessary to move this common logic into a separate
> place which is independent of {{GridMapQueryExecutor}}.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
