You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@phoenix.apache.org by "ASF GitHub Bot (JIRA)" <ji...@apache.org> on 2016/12/27 18:34:58 UTC

[jira] [Commented] (PHOENIX-852) Optimize child/parent foreign key joins

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

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

Github user maryannxue closed the pull request at:

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


> 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
>             Fix For: 4.2.0, 3.2.0
>
>         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)