[ https://issues.apache.org/jira/browse/PHOENIX-1556?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16361630#comment-16361630 ]
Hudson commented on PHOENIX-1556: --------------------------------- FAILURE: Integrated in Jenkins build Phoenix-master #1934 (See [https://builds.apache.org/job/Phoenix-master/1934/]) PHOENIX-1556 Base hash versus sort merge join decision on cost (maryannxue: rev 9461d0d6a299bb3cbcf53905d7e9b73895a99299) * (edit) phoenix-core/src/it/java/org/apache/phoenix/end2end/CostBasedDecisionIT.java * (edit) phoenix-core/src/main/java/org/apache/phoenix/util/CostUtil.java * (edit) phoenix-core/src/main/java/org/apache/phoenix/compile/QueryPlan.java * (edit) phoenix-core/src/main/java/org/apache/phoenix/execute/SortMergeJoinPlan.java * (edit) phoenix-core/src/main/java/org/apache/phoenix/execute/UnionPlan.java * (add) phoenix-core/src/main/java/org/apache/phoenix/execute/visitor/AvgRowWidthVisitor.java * (add) phoenix-core/src/main/java/org/apache/phoenix/execute/visitor/RowCountVisitor.java * (edit) phoenix-core/src/test/java/org/apache/phoenix/query/ParallelIteratorsSplitTest.java * (edit) phoenix-core/src/main/java/org/apache/phoenix/jdbc/PhoenixStatement.java * (add) phoenix-core/src/main/java/org/apache/phoenix/execute/visitor/ByteCountVisitor.java * (edit) phoenix-core/src/main/java/org/apache/phoenix/execute/CorrelatePlan.java * (edit) phoenix-core/src/main/java/org/apache/phoenix/compile/QueryCompiler.java * (edit) phoenix-core/src/main/java/org/apache/phoenix/execute/LiteralResultIterationPlan.java * (edit) phoenix-core/src/main/java/org/apache/phoenix/execute/ScanPlan.java * (add) phoenix-core/src/main/java/org/apache/phoenix/execute/visitor/QueryPlanVisitor.java * (edit) phoenix-core/src/main/java/org/apache/phoenix/execute/AggregatePlan.java * (edit) phoenix-core/src/main/java/org/apache/phoenix/execute/ClientProcessingPlan.java * (edit) phoenix-core/src/main/java/org/apache/phoenix/compile/ListJarsQueryPlan.java * (edit) phoenix-core/src/main/java/org/apache/phoenix/compile/JoinCompiler.java * (edit) phoenix-core/src/main/java/org/apache/phoenix/execute/ClientAggregatePlan.java * (edit) phoenix-core/src/main/java/org/apache/phoenix/execute/UnnestArrayPlan.java * (edit) phoenix-core/src/main/java/org/apache/phoenix/execute/ClientScanPlan.java * (edit) phoenix-core/src/main/java/org/apache/phoenix/execute/TupleProjectionPlan.java * (edit) phoenix-core/src/main/java/org/apache/phoenix/execute/HashJoinPlan.java * (edit) phoenix-core/src/main/java/org/apache/phoenix/compile/TraceQueryPlan.java * (edit) phoenix-core/src/main/java/org/apache/phoenix/execute/CursorFetchPlan.java > Base hash versus sort merge join decision on cost > ------------------------------------------------- > > Key: PHOENIX-1556 > URL: https://issues.apache.org/jira/browse/PHOENIX-1556 > Project: Phoenix > Issue Type: Sub-task > Reporter: James Taylor > Assignee: Maryann Xue > Priority: Major > Labels: CostBasedOptimization > Attachments: PHOENIX-1556.patch > > > At compile time, we know how many guideposts (i.e. how many bytes) will be > scanned for the RHS table. We should, by default, base the decision of using > the hash-join verus many-to-many join on this information. > Another criteria (as we've seen in PHOENIX-4508) is whether or not the tables > being joined are already ordered by the join key. In that case, it's better > to always use the sort merge join. -- This message was sent by Atlassian JIRA (v7.6.3#76005)