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

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

{panel:title=Branch: [pull/10077/head] Base: [master] : No blockers 
found!|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}{panel}
{panel:title=Branch: [pull/10077/head] Base: [master] : New Tests 
(2)|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}
{color:#00008b}Queries 1 (lazy=true){color} [[tests 
1|https://ci.ignite.apache.org/viewLog.html?buildId=6617415]]
* {color:#013220}IgniteBinaryCacheQueryLazyTestSuite: 
GridSubqueryJoinOptimizerSelfTest.testOptimizationLeftJoinSubqueryOnLeft - 
PASSED{color}

{color:#00008b}Queries 1{color} [[tests 
1|https://ci.ignite.apache.org/viewLog.html?buildId=6619709]]
* {color:#013220}IgniteBinaryCacheQueryTestSuite: 
GridSubqueryJoinOptimizerSelfTest.testOptimizationLeftJoinSubqueryOnLeft - 
PASSED{color}

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

> Wrong result if subquery is on the left child of LEFT JOIN operator
> -------------------------------------------------------------------
>
>                 Key: IGNITE-17131
>                 URL: https://issues.apache.org/jira/browse/IGNITE-17131
>             Project: Ignite
>          Issue Type: Bug
>          Components: sql
>    Affects Versions: 2.13
>            Reporter: Konstantin Orlov
>            Assignee: Konstantin Orlov
>            Priority: Critical
>          Time Spent: 10m
>  Remaining Estimate: 0h
>
> Currently a query with a filtering subquery of a left side of a LEFT JOIN 
> returns an invalid result. Looks like the problem is somewhere inside 
> {{{}GridSubqueryJoinOptimizer{}}}.
> The possible workaround is to turn the join rewriting off by setting the 
> system property {{IGNITE_ENABLE_SUBQUERY_REWRITE_OPTIMIZATION}} to false.



--
This message was sent by Atlassian Jira
(v8.20.7#820007)

Reply via email to