[
https://issues.apache.org/jira/browse/TAJO-1013?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14102387#comment-14102387
]
ASF GitHub Bot commented on TAJO-1013:
--------------------------------------
GitHub user hyunsik opened a pull request:
https://github.com/apache/tajo/pull/123
TAJO-1013: A complex equality condition including columns of the same table
is recognized as a join condition.
See the jira.
https://issues.apache.org/jira/browse/TAJO-1013
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/hyunsik/tajo 1013
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/tajo/pull/123.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 #123
----
commit fb5c8817819a4e29d4406b07874ece30fca4f965
Author: Hyunsik Choi <[email protected]>
Date: 2014-08-19T16:07:32Z
Fixed the bug.
commit 83cdb6e64ab8be4b04d3ff63fb10901c9b2976a3
Author: Hyunsik Choi <[email protected]>
Date: 2014-08-19T16:16:56Z
Merge branch 'master' of https://git-wip-us.apache.org/repos/asf/tajo into
TAJO-103
Conflicts:
tajo-core/src/main/java/org/apache/tajo/engine/eval/EvalTreeUtil.java
----
> 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)
