[
https://issues.apache.org/jira/browse/TAJO-884?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14044295#comment-14044295
]
Hudson commented on TAJO-884:
-----------------------------
SUCCESS: Integrated in Tajo-master-build #265 (See
[https://builds.apache.org/job/Tajo-master-build/265/])
TAJO-884: complex join conditions should be supported in ON clause. (hyunsik:
rev b3758361335a4cd26d8b7b9d18879b2b35f612fb)
*
tajo-core/src/test/resources/queries/TestJoinBroadcast/testLeftOuterJoinWithConstantExpr3.sql
* tajo-core/src/main/java/org/apache/tajo/engine/planner/LogicalPlan.java
* tajo-core/src/main/java/org/apache/tajo/engine/planner/ExprNormalizer.java
* CHANGES
*
tajo-core/src/test/resources/queries/TestJoinQuery/testComplexJoinCondition1.sql
*
tajo-core/src/test/resources/queries/TestJoinQuery/testComplexJoinCondition4.sql
* tajo-core/src/test/resources/queries/TestJoinQuery/table1_int4_ddl.sql
* tajo-core/src/test/java/org/apache/tajo/engine/query/TestCreateTable.java
*
tajo-core/src/test/resources/results/TestJoinQuery/testComplexJoinCondition3.result
*
tajo-core/src/test/resources/queries/TestJoinQuery/testComplexJoinCondition2.sql
*
tajo-core/src/test/resources/queries/TestJoinQuery/testLeftOuterJoinWithConstantExpr3.sql
*
tajo-core/src/main/java/org/apache/tajo/engine/planner/rewrite/ProjectionPushDownRule.java
* tajo-core/src/main/java/org/apache/tajo/engine/planner/ExprAnnotator.java
* tajo-core/src/main/java/org/apache/tajo/engine/planner/LogicalPlanner.java
*
tajo-core/src/test/resources/results/TestJoinQuery/testComplexJoinCondition4.result
*
tajo-core/src/test/resources/results/TestJoinQuery/testComplexJoinCondition2.result
*
tajo-core/src/test/resources/results/TestJoinQuery/testComplexJoinCondition1.result
* tajo-core/src/main/java/org/apache/tajo/engine/eval/EvalTreeUtil.java
*
tajo-core/src/main/java/org/apache/tajo/engine/planner/logical/join/JoinGraph.java
* tajo-core/src/test/java/org/apache/tajo/engine/query/TestJoinQuery.java
*
tajo-core/src/test/resources/queries/TestJoinQuery/testComplexJoinCondition3.sql
*
tajo-core/src/test/resources/results/TestJoinQuery/testDifferentTypesJoinCondition.result
*
tajo-core/src/test/resources/queries/TestJoinQuery/testDifferentTypesJoinCondition.sql
* tajo-core/src/test/resources/queries/TestJoinQuery/table1_int8_ddl.sql
> complex join conditions should be supported in ON clause
> --------------------------------------------------------
>
> Key: TAJO-884
> URL: https://issues.apache.org/jira/browse/TAJO-884
> Project: Tajo
> Issue Type: Bug
> Components: planner/optimizer
> Reporter: Hyunsik Choi
> Assignee: Hyunsik Choi
> Fix For: 0.9.0
>
>
> join condition can be complex expressions instead of simple equi-join
> condition of fields.
> See the example where t3.id is INT4 and t4.id INT8. In this case, t3.id and
> t4.id are different but compatible to each other. In this case, current
> planner handles the expression incorrectly.
> {code}
> select * from table3 t3 join table4 t4 on t3.id = t4.id;
> {code}
> Also, please see the following example. Currently, the following join
> condition does not work.
> {code}
> select * from table3 t3 join table4 t4 on substr(t3.key, 1, 4) = t4.key;
> {code}
--
This message was sent by Atlassian JIRA
(v6.2#6252)
