You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@phoenix.apache.org by "James Taylor (JIRA)" <ji...@apache.org> on 2014/09/01 00:52:20 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=14116930#comment-14116930 ]
James Taylor commented on PHOENIX-852:
--------------------------------------
Looks good, [~maryannxue]. See my comment on PHOENIX-1220 - it'd be good to adjust your getSampleValue call to take that into account prior to checking this in. +1 after that.
> 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.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)