[
https://issues.apache.org/jira/browse/TAJO-1277?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14323572#comment-14323572
]
Hudson commented on TAJO-1277:
------------------------------
FAILURE: Integrated in Tajo-master-CODEGEN-build #224 (See
[https://builds.apache.org/job/Tajo-master-CODEGEN-build/224/])
TAJO-1277: GreedyHeuristicJoinOrderAlgorithm sometimes wrongly assumes
associativity of joins. (Keuntae Park via jihoon) (jihoonson: rev
95d9cc455dd7d25da6dd0df709084d7346efb410)
*
tajo-plan/src/main/java/org/apache/tajo/plan/joinorder/GreedyHeuristicJoinOrderAlgorithm.java
*
tajo-core/src/test/resources/results/TestJoinQuery/testJoinWithMultipleJoinTypes.result
* tajo-core/src/test/java/org/apache/tajo/engine/query/TestJoinQuery.java
*
tajo-core/src/test/resources/queries/TestJoinQuery/testJoinWithMultipleJoinTypes.sql
* CHANGES
> GreedyHeuristicJoinOrderAlgorithm sometimes wrongly assumes associativity of
> joins
> ----------------------------------------------------------------------------------
>
> Key: TAJO-1277
> URL: https://issues.apache.org/jira/browse/TAJO-1277
> Project: Tajo
> Issue Type: Bug
> Reporter: Keuntae Park
> Assignee: Keuntae Park
>
> It looks like GreedyHeuristicJoinOrderAlgorithm always assumes every joins
> are associative.
> Following query returns in inaccurate result:
> {code}
> select * FROM
> customer c
> right outer join nation n on c.c_custkey = n.n_nationkey
> join region r on c.c_custkey = r.r_regionkey;
> {code}
> because GreedyHeuristicJoinOrderAlgorithm changes join order as
> {code}
> select * FROM
> customer c
> join region r on c.c_custkey = r.r_regionkey
> right outer join nation n on c.c_custkey = n.n_nationkey;
> {code}
> I think getBestPair() should be fixed to avoid wrong join ordering.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
