[
https://issues.apache.org/jira/browse/TAJO-884?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Hyunsik Choi updated TAJO-884:
------------------------------
Description:
join condition can be complex expressions instead of simple equi-join condition
of fields.
See the example where t3.id is INT4 and t4.id INT8. In this case, t3.id and
t4.id are different but compatible to each other. In this case, current
planner handles the expression incorrectly.
{code}
select * from table3 t3 join table4 t4 on t3.id = t4.id;
{code}
Also, please see the following example. Currently, the following join condition
does not work.
{code}
select * from table3 t3 join table4 t4 on substr(t3.key, 1, 4) = t4.key;
{code}
was:
See the example where t3.id is INT4 and t4.id INT8. In this case, t3.id and
t4.id are different but compatible to each other.
In this case, current planner handles the expression incorrectly. As a result,
the cross join plan is generated. We should fix it.
{code}
select * from table3 t3 join table4 t4 on t3.id = t4.id;
{code}
> complex join conditions should be supported in ON clause
> --------------------------------------------------------
>
> Key: TAJO-884
> URL: https://issues.apache.org/jira/browse/TAJO-884
> Project: Tajo
> Issue Type: Bug
> Components: planner/optimizer
> Reporter: Hyunsik Choi
> Assignee: Hyunsik Choi
> Priority: Minor
> Fix For: 0.9.0
>
>
> join condition can be complex expressions instead of simple equi-join
> condition of fields.
> See the example where t3.id is INT4 and t4.id INT8. In this case, t3.id and
> t4.id are different but compatible to each other. In this case, current
> planner handles the expression incorrectly.
> {code}
> select * from table3 t3 join table4 t4 on t3.id = t4.id;
> {code}
> Also, please see the following example. Currently, the following join
> condition does not work.
> {code}
> select * from table3 t3 join table4 t4 on substr(t3.key, 1, 4) = t4.key;
> {code}
--
This message was sent by Atlassian JIRA
(v6.2#6252)
