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/03/19 17:51:47 UTC

[jira] [Updated] (PHOENIX-632) Support equi-joins through broadcast hash join

     [ https://issues.apache.org/jira/browse/PHOENIX-632?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

James Taylor updated PHOENIX-632:
---------------------------------

    Summary: Support equi-joins through broadcast hash join  (was: Support joins through broadcast hash join)

> Support equi-joins through broadcast hash join
> ----------------------------------------------
>
>                 Key: PHOENIX-632
>                 URL: https://issues.apache.org/jira/browse/PHOENIX-632
>             Project: Phoenix
>          Issue Type: New Feature
>    Affects Versions: 3.0.0, 4.0.0, 5.0.0
>            Reporter: Maryann Xue
>            Priority: Blocker
>             Fix For: 3.0.0, 4.0.0, 5.0.0
>
>
> The main impact on interfaces in the current master:
> 1. QueryCompiler: the original logic of compile() now goes into compileSingleQuery(), and the call compile() is now used as entry for both single select statements and join statements. Join statement compilation might go through recursive calls of compileSingleQuery() and compileJoinQuery().
> 2. ServerCacheClient: the original interface takes a TableRef in the constructor, while the parameter has now been moved to addServerCache(), for the reason that we might want to reuse ServerCacheClient for multiple calls in completing a query, and the parameter "cacheUsingTableRef" could be different among these multiple calls.



--
This message was sent by Atlassian JIRA
(v6.2#6252)