phoenix-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hudson (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (PHOENIX-1556) Base hash versus sort merge join decision on cost
Date Wed, 14 Mar 2018 13:39:01 GMT

    [ https://issues.apache.org/jira/browse/PHOENIX-1556?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16398601#comment-16398601
] 

Hudson commented on PHOENIX-1556:
---------------------------------

FAILURE: Integrated in Jenkins build Phoenix-4.x-HBase-0.98 #1833 (See [https://builds.apache.org/job/Phoenix-4.x-HBase-0.98/1833/])
PHOENIX-1556 Base hash versus sort merge join decision on cost (maryannxue: rev 6914d54d99b4fafae44d1a3397c44ba6e5d10368)
* (edit) phoenix-core/src/main/java/org/apache/phoenix/execute/SortMergeJoinPlan.java
* (edit) phoenix-core/src/main/java/org/apache/phoenix/execute/CorrelatePlan.java
* (edit) phoenix-core/src/main/java/org/apache/phoenix/execute/LiteralResultIterationPlan.java
* (edit) phoenix-core/src/main/java/org/apache/phoenix/compile/TraceQueryPlan.java
* (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/test/java/org/apache/phoenix/query/ParallelIteratorsSplitTest.java
* (edit) phoenix-core/src/main/java/org/apache/phoenix/execute/ClientProcessingPlan.java
* (edit) phoenix-core/src/main/java/org/apache/phoenix/compile/QueryPlan.java
* (add) phoenix-core/src/main/java/org/apache/phoenix/execute/visitor/ByteCountVisitor.java
* (edit) phoenix-core/src/main/java/org/apache/phoenix/jdbc/PhoenixStatement.java
* (edit) phoenix-core/src/main/java/org/apache/phoenix/execute/UnnestArrayPlan.java
* (add) phoenix-core/src/main/java/org/apache/phoenix/execute/visitor/QueryPlanVisitor.java
* (edit) phoenix-core/src/main/java/org/apache/phoenix/execute/UnionPlan.java
* (edit) phoenix-core/src/main/java/org/apache/phoenix/execute/ClientScanPlan.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/TupleProjectionPlan.java
* (edit) phoenix-core/src/main/java/org/apache/phoenix/compile/QueryCompiler.java
* (edit) phoenix-core/src/main/java/org/apache/phoenix/execute/ScanPlan.java
* (edit) phoenix-core/src/main/java/org/apache/phoenix/execute/CursorFetchPlan.java
* (edit) phoenix-core/src/main/java/org/apache/phoenix/execute/HashJoinPlan.java
* (edit) phoenix-core/src/main/java/org/apache/phoenix/execute/AggregatePlan.java
* (edit) phoenix-core/src/main/java/org/apache/phoenix/compile/ListJarsQueryPlan.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


> 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
>             Fix For: 4.14.0, 5.0.0
>
>         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)

Mime
View raw message