[
https://issues.apache.org/jira/browse/IMPALA-13429?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17889827#comment-17889827
]
ASF subversion and git services commented on IMPALA-13429:
----------------------------------------------------------
Commit 32cec3fd80b129e4d84a403f1ee0c4144101f80c in impala's branch
refs/heads/master from Steve Carlin
[ https://gitbox.apache.org/repos/asf?p=impala.git;h=32cec3fd8 ]
IMPALA-13429: Calcite planner crashing with outer join
The Calcite planner was crashing when there was an outer join
and there was a conjunct that compared two columns within the
same table. This conjunct needs to be place in "other" conjuncts
rather than "equi" conjuncts.
Change-Id: I4ae2d257fa58f3a58079b6aa551c32ffda7d28cf
Reviewed-on: http://gerrit.cloudera.org:8080/21908
Reviewed-by: Michael Smith <[email protected]>
Tested-by: Michael Smith <[email protected]>
> Calcite planner: Outer join query with nonequi conjunct crashes Impala server
> -----------------------------------------------------------------------------
>
> Key: IMPALA-13429
> URL: https://issues.apache.org/jira/browse/IMPALA-13429
> Project: IMPALA
> Issue Type: Sub-task
> Reporter: Steve Carlin
> Priority: Major
> Fix For: Impala 4.5.0
>
>
> The server is crashing on the following query:
> select * from alltypesagg a left join altypesagg_dup b on (a.id = b.id and
> a.month = a.id)
> The reason is because "a.month=a.id" is being treated as an "equiconjunct",
> meaning that it places this conjunct as a join between two different tables.
> But this conjunct compares two columns in the same table.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]