[
https://issues.apache.org/jira/browse/IGNITE-12484?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17015993#comment-17015993
]
Ignite TC Bot commented on IGNITE-12484:
----------------------------------------
{panel:title=Branch: [pull/7183/head] Base: [master] : Possible Blockers
(2)|borderStyle=dashed|borderColor=#ccc|titleBGColor=#F7D6C1}
{color:#d04437}Continuous Query 1{color} [[tests
2|https://ci.ignite.apache.org/viewLog.html?buildId=4869127]]
* IgniteCacheQuerySelfTestSuite3:
CacheContinuousQueryFailoverAtomicNearEnabledSelfSelfTest.testMultiThreadedFailover
- New test duration 63s is more that 1 minute
* IgniteCacheQuerySelfTestSuite3:
CacheContinuousQueryFailoverAtomicNearEnabledSelfSelfTest.testFailoverStartStopBackup
- New test duration 63s is more that 1 minute
{panel}
[TeamCity *--> Run :: All*
Results|https://ci.ignite.apache.org/viewLog.html?buildId=4869232&buildTypeId=IgniteTests24Java8_RunAll]
> Fix issues related to client cache stop and SQL metadata retrieval
> ------------------------------------------------------------------
>
> Key: IGNITE-12484
> URL: https://issues.apache.org/jira/browse/IGNITE-12484
> Project: Ignite
> Issue Type: Bug
> Components: sql
> Affects Versions: 2.7
> Reporter: Taras Ledkov
> Assignee: Taras Ledkov
> Priority: Major
> Fix For: 2.8
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> After IGNITE-6173 the problem is appeared. We need to fix it by properly
> handling client cache stop. Main idea is that SQL schema metadata (tables,
> indexes, etc.) should not be removed on client cache.close().
> But the implementation should be carefully designed as many factors should be
> taken into account, e.g. cache destroy, persistence, client reconnect and etc.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
