[
https://issues.apache.org/jira/browse/TAJO-884?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14040536#comment-14040536
]
ASF GitHub Bot commented on TAJO-884:
-------------------------------------
GitHub user hyunsik opened a pull request:
https://github.com/apache/tajo/pull/44
TAJO-884: complex join conditions should be supported in ON clause.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/hyunsik/tajo TAJO-884
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/tajo/pull/44.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #44
----
commit 4965cd6a36e13accc4541b7aae8a3582988c42e3
Author: Hyunsik Choi <[email protected]>
Date: 2014-06-23T08:54:00Z
TAJO-884: complex join conditions should be supported in ON clause.
----
> 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)
