[
https://issues.apache.org/jira/browse/TAJO-1013?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14103765#comment-14103765
]
Hudson commented on TAJO-1013:
------------------------------
SUCCESS: Integrated in Tajo-master-build #342 (See
[https://builds.apache.org/job/Tajo-master-build/342/])
TAJO-1013: a complex equality condition including columns of the same table is
recognized as a join condition. (hyunsik: rev
7c84aeb298919ac0e6a1eb1c469ae830656f17fa)
*
tajo-core/src/test/resources/results/TestSelectQuery/testColumnEqualityButNotJoinCondition2.result
*
tajo-core/src/test/resources/results/TestSelectQuery/testColumnEqualityButNotJoinCondition1.result
* CHANGES
*
tajo-core/src/test/resources/queries/TestSelectQuery/testColumnEqualityButNotJoinCondition2.sql
* tajo-core/src/test/java/org/apache/tajo/engine/eval/TestEvalTreeUtil.java
*
tajo-core/src/main/java/org/apache/tajo/engine/planner/LogicalPlanPreprocessor.java
*
tajo-core/src/main/java/org/apache/tajo/engine/planner/logical/join/JoinGraph.java
* tajo-core/src/main/java/org/apache/tajo/engine/eval/EvalTreeUtil.java
*
tajo-core/src/test/resources/queries/TestSelectQuery/testColumnEqualityButNotJoinCondition1.sql
*
tajo-core/src/main/java/org/apache/tajo/engine/planner/rewrite/FilterPushDownRule.java
* tajo-core/src/test/java/org/apache/tajo/engine/query/TestSelectQuery.java
* tajo-core/src/main/java/org/apache/tajo/engine/planner/ExprFinder.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)
