[
https://issues.apache.org/jira/browse/IGNITE-11918?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16865587#comment-16865587
]
Ignite TC Bot commented on IGNITE-11918:
----------------------------------------
{panel:title=--> Run :: All: Possible
Blockers|borderStyle=dashed|borderColor=#ccc|titleBGColor=#F7D6C1}
{color:#d04437}Platform .NET{color} [[tests 1 TIMEOUT
|https://ci.ignite.apache.org/viewLog.html?buildId=4118701]]
{color:#d04437}[Check Code Style]{color} [[tests 0 Exit Code
|https://ci.ignite.apache.org/viewLog.html?buildId=4118729]]
{panel}
[TeamCity *--> Run :: All*
Results|https://ci.ignite.apache.org/viewLog.html?buildId=4118730&buildTypeId=IgniteTests24Java8_RunAll]
> extend test coverage for KILL QUERY
> -----------------------------------
>
> Key: IGNITE-11918
> URL: https://issues.apache.org/jira/browse/IGNITE-11918
> Project: Ignite
> Issue Type: Test
> Reporter: Pavel Kuznetsov
> Assignee: Pavel Kuznetsov
> Priority: Major
> Time Spent: 10m
> Remaining Estimate: 0h
>
> Currently we have implemented KILL QUERY COMMAND. However not all cases
> covered by tests and probably it doesn't work properly for all cases.
> On first look need to add following test scenarios for KILL QUERY command:
> 1) not stable topology - when node couldn't reserve partitions.
> 2) map and reduce parts
> 3) with concrete partition
> 4) when partition pruning is work.
> 5) local query
> 6) distributed joins.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
