[
https://issues.apache.org/jira/browse/ARROW-10965?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Daniël Heres updated ARROW-10965:
---------------------------------
Description:
If we switch the order of keys in a equijoin this results in an error. It seems
that some code assumes that the left key in the expression is in the left input
of the join and the right key comes from the right side.
For example changing l_orderkey = o_orderkey to
o_orderkey = l_orderkey
in query 12 of the tpch benchmark, we get this error:
{{Error: Plan("The left or right side of the join does not have all columns on
\"on\": \nMissing on the left: \{\"o_orderkey\"}\nMissing on the right:
\{\"l_orderkey\"}")}}
was:
If we switch the order of keys in a equijoin this results in an error.
For example changing l_orderkey = o_orderkey to
o_orderkey = l_orderkey
in query 12 of the tpch benchmark, we get this error:
{{Error: Plan("The left or right side of the join does not have all columns on
\"on\": \nMissing on the left: \{\"o_orderkey\"}\nMissing on the right:
\{\"l_orderkey\"}")}}
> [Rust][DataFusion] switching key join order results in error
> ------------------------------------------------------------
>
> Key: ARROW-10965
> URL: https://issues.apache.org/jira/browse/ARROW-10965
> Project: Apache Arrow
> Issue Type: Bug
> Components: Rust - DataFusion
> Reporter: Daniël Heres
> Priority: Minor
>
> If we switch the order of keys in a equijoin this results in an error. It
> seems that some code assumes that the left key in the expression is in the
> left input of the join and the right key comes from the right side.
> For example changing l_orderkey = o_orderkey to
> o_orderkey = l_orderkey
> in query 12 of the tpch benchmark, we get this error:
>
> {{Error: Plan("The left or right side of the join does not have all columns
> on \"on\": \nMissing on the left: \{\"o_orderkey\"}\nMissing on the right:
> \{\"l_orderkey\"}")}}
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
