phoenix-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF GitHub Bot (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (PHOENIX-852) Optimize child/parent foreign key joins
Date Tue, 19 Aug 2014 03:10:18 GMT

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

ASF GitHub Bot commented on PHOENIX-852:
----------------------------------------

GitHub user maryannxue opened a pull request:

    https://github.com/apache/phoenix/pull/7

    PHOENIX-852 Optimize child/parent foreign key joins

    

You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/maryannxue/phoenix master

Alternatively you can review and apply these changes as the patch at:

    https://github.com/apache/phoenix/pull/7.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

    This closes #7
    
----
commit c89d815f64bba2cd85a2b03ed200338f9a47f63e
Author: maryannxue <maryannxue@apache.org>
Date:   2014-08-19T03:04:00Z

    PHOENIX-852 Optimize child/parent foreign key joins

----


> 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
>
> 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.2#6252)

Mime
View raw message