You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@tajo.apache.org by "Hyunsik Choi (JIRA)" <ji...@apache.org> on 2014/06/23 09:39:24 UTC

[jira] [Updated] (TAJO-884) complex join conditions should be supported ON clause

     [ https://issues.apache.org/jira/browse/TAJO-884?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Hyunsik Choi updated TAJO-884:
------------------------------

    Summary: complex join conditions should be supported ON clause  (was: An join condition with compatible types should be supported)

> complex join conditions should be supported 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
>
>
> 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}



--
This message was sent by Atlassian JIRA
(v6.2#6252)