[
https://issues.apache.org/jira/browse/TAJO-1013?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14103422#comment-14103422
]
ASF GitHub Bot commented on TAJO-1013:
--------------------------------------
Github user blrunner commented on the pull request:
https://github.com/apache/tajo/pull/123#issuecomment-52736347
+1
Thanks your contribution.
It looks good to me and 'mvn clean install' finished successfully.
> A complex equality condition including columns of the same table is
> recognized as a join condition
> --------------------------------------------------------------------------------------------------
>
> Key: TAJO-1013
> URL: https://issues.apache.org/jira/browse/TAJO-1013
> Project: Tajo
> Issue Type: Bug
> Components: planner/optimizer
> Reporter: Hyunsik Choi
> Assignee: Hyunsik Choi
> Priority: Trivial
> Fix For: 0.9.0
>
>
> See the following example:
> {code}
> SELECT
> t1.str1, t1.str2, t2.abc
> FROM
> table1 t1, table2 t2
> WHERE t1.id = t2.id and substr(t1.str1, 1, 3) = substr(t1.str2, 1,3);
> {code}
> Currently, the expression {{substr(t1.str1, 1, 3) = substr(t1.str2, 1,3);}}
> is also addressed as a join condition. Since it includes columns of the same
> table, we shouldn't do it.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
