[
https://issues.apache.org/jira/browse/TAJO-1009?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14100227#comment-14100227
]
ASF GitHub Bot commented on TAJO-1009:
--------------------------------------
GitHub user hyunsik opened a pull request:
https://github.com/apache/tajo/pull/121
TAJO-1009: A binary eval for column references of the same tables should...
... not be recognized as a join condition.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/hyunsik/tajo TAJO-1009
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/tajo/pull/121.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 #121
----
commit 51c0c3a358e586f772bd1880f45d7d0000f3970c
Author: Hyunsik Choi <[email protected]>
Date: 2014-08-18T02:30:39Z
TAJO-1009: A binary eval for column references of the same tables should
not be recognized as a join condition.
----
> A binary eval for column references of the same tables should not be
> recognized as a join condition
> ---------------------------------------------------------------------------------------------------
>
> Key: TAJO-1009
> URL: https://issues.apache.org/jira/browse/TAJO-1009
> 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 a,b,c from table1 where table1.a > table1.b;
> {code}
> EvalTreeUtil.isJoinQual recognizes the above predicate as a join qual. It's
> wrong.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
