[
https://issues.apache.org/jira/browse/TAJO-1009?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14100509#comment-14100509
]
Hudson commented on TAJO-1009:
------------------------------
FAILURE: Integrated in Tajo-master-build #339 (See
[https://builds.apache.org/job/Tajo-master-build/339/])
TAJO-1009: A binary eval for column references of the same tables should not be
recognized as a join condition. (hyunsik: rev
96b6c2aad76837c42d894b4aa217c6641e72ec86)
* CHANGES
* tajo-core/src/test/java/org/apache/tajo/engine/eval/TestEvalTreeUtil.java
* tajo-core/src/main/java/org/apache/tajo/engine/eval/EvalTreeUtil.java
> 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)
