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

Ignite TC Bot commented on IGNITE-16629:
----------------------------------------

{panel:title=Branch: [pull/9857/head] Base: [master] : No blockers 
found!|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}{panel}
{panel:title=Branch: [pull/9857/head] Base: [master] : New Tests 
(2)|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}
{color:#00008b}Continuous Query 4{color} [[tests 
2|https://ci.ignite.apache.org/viewLog.html?buildId=6434589]]
* {color:#013220}IgniteCacheQuerySelfTestSuite6: 
IgniteSqlSinglePartitionMultiParallelismTest.testMultiPartitionedRdcMonoPartitionedMap
 - PASSED{color}
* {color:#013220}IgniteCacheQuerySelfTestSuite6: 
IgniteSqlSinglePartitionMultiParallelismTest.testWhereCountPartitionQuery - 
PASSED{color}

{panel}
[TeamCity *--> Run :: All* 
Results|https://ci.ignite.apache.org/viewLog.html?buildId=6434663&buildTypeId=IgniteTests24Java8_RunAll]

> Wrong calculation of replies count for queries with partition pruning and 
> enabled parallelism
> ---------------------------------------------------------------------------------------------
>
>                 Key: IGNITE-16629
>                 URL: https://issues.apache.org/jira/browse/IGNITE-16629
>             Project: Ignite
>          Issue Type: Bug
>          Components: sql
>            Reporter: Yury Gerzhedovich
>            Assignee: Yury Gerzhedovich
>            Priority: Critical
>          Time Spent: 10m
>  Remaining Estimate: 0h
>
> Currently a simple query is freezing forever if query parallelism is enabled 
> and partition pruning extracts more than one partition. This caused by wrong 
> replies count estimation made on a reducer node.
> The problematic query looks like this: {{{}select * from t where aff_key in 
> ('a', 'b', 'c'){}}}.
> Please note that field _aff_key_ should be an affinity key and be a part of 
> the compound PK.



--
This message was sent by Atlassian Jira
(v8.20.1#820001)

Reply via email to