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-852) Optimize child/parent foreign key joins
Date Tue, 02 Sep 2014 15:33:20 GMT

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

Hudson commented on PHOENIX-852:
--------------------------------

SUCCESS: Integrated in Phoenix | Master | Hadoop1 #353 (See [https://builds.apache.org/job/Phoenix-master-hadoop1/353/])
PHOENIX-852 Optimize child/parent foreign key joins (maryannxue: rev 27a6ccef31b3fa7fd4ca4a4e9cb9bc01ae498238)
* phoenix-core/src/test/java/org/apache/phoenix/schema/PDataTypeTest.java
* phoenix-core/src/main/java/org/apache/phoenix/parse/HintNode.java
* phoenix-core/src/main/java/org/apache/phoenix/schema/PArrayDataType.java
* phoenix-core/src/main/java/org/apache/phoenix/compile/ScanRanges.java
* phoenix-core/src/main/java/org/apache/phoenix/schema/PDataType.java
* phoenix-core/src/main/java/org/apache/phoenix/compile/JoinCompiler.java
* phoenix-core/src/main/java/org/apache/phoenix/compile/QueryCompiler.java
* phoenix-core/src/main/java/org/apache/phoenix/execute/HashJoinPlan.java
* phoenix-core/src/main/java/org/apache/phoenix/compile/WhereOptimizer.java
* phoenix-core/src/main/java/org/apache/phoenix/join/HashCacheClient.java
* phoenix-core/src/it/java/org/apache/phoenix/end2end/HashJoinIT.java
* phoenix-core/src/main/java/org/apache/phoenix/compile/WhereCompiler.java


> Optimize child/parent foreign key joins
> ---------------------------------------
>
>                 Key: PHOENIX-852
>                 URL: https://issues.apache.org/jira/browse/PHOENIX-852
>             Project: Phoenix
>          Issue Type: Improvement
>            Reporter: James Taylor
>            Assignee: Maryann Xue
>         Attachments: 852-2.patch, 852-3.patch, 852-4.patch, 852.patch, PHOENIX-852.patch
>
>
> Often times a join will occur from a child to a parent. Our current algorithm would do
a full scan of one side or the other. We can do much better than that if the HashCache contains
the PK (or even part of the PK) from the table being joined to. In these cases, we should
drive the second scan through a skip scan on the server side.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message