You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@calcite.apache.org by GitBox <gi...@apache.org> on 2020/05/07 23:40:41 UTC

[GitHub] [calcite] rkondakov commented on a change in pull request #1953: [CALCITE-3896] Top down trait request

rkondakov commented on a change in pull request #1953:
URL: https://github.com/apache/calcite/pull/1953#discussion_r421854785



##########
File path: core/src/test/java/org/apache/calcite/tools/PlannerTest.java
##########
@@ -1030,10 +1030,12 @@ private void checkJoinNWay(int n) throws Exception {
         + "EnumerableProject(empid=[$2], deptno=[$3], name=[$4], salary=[$5], commission=[$6], deptno0=[$7], name0=[$8], employees=[$9], location=[ROW($10, $11)], empid0=[$0], name1=[$1])\n"
         + "  EnumerableHashJoin(condition=[=($0, $2)], joinType=[left])\n"
         + "    EnumerableTableScan(table=[[hr, dependents]])\n"
-        + "    EnumerableHashJoin(condition=[=($1, $5)], joinType=[inner])\n"
-        + "      EnumerableTableScan(table=[[hr, emps]])\n"
-        + "      EnumerableProject(deptno=[$0], name=[$1], employees=[$2], x=[$3.x], y=[$3.y])\n"
-        + "        EnumerableTableScan(table=[[hr, depts]])";
+        + "    EnumerableMergeJoin(condition=[=($1, $5)], joinType=[inner])\n"

Review comment:
       Why hash join is switched to merge join? It looks a bit weird because inputs are not sorted and we have to sort them explicitly which is a heavy task. Can it be a sign of some bug?




----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

For queries about this service, please contact Infrastructure at:
users@infra.apache.org