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 2015/01/14 19:00:43 UTC

[jira] [Commented] (PHOENIX-1560) Join between global index and data table if INDEX hint used

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

James Taylor commented on PHOENIX-1560:
---------------------------------------

Patch looks good - thanks for the quick turnaround, [~maryannxue]. One comment/question:
- If the query has no where clause, but is ordered by the pk of the index, wouldn't it make sense for the optimization to kick in?


> Join between global index and data table if INDEX hint used
> -----------------------------------------------------------
>
>                 Key: PHOENIX-1560
>                 URL: https://issues.apache.org/jira/browse/PHOENIX-1560
>             Project: Phoenix
>          Issue Type: Bug
>            Reporter: James Taylor
>            Assignee: Maryann Xue
>         Attachments: 1560.patch
>
>
> We already have an INDEX hint, and we already have a mechanism to collect referenced columns in the data table that are not in the index table (used only for local indexes currently). Instead of not using the global index when a referenced data column is not found in the index, we should rewrite the query to join back to the data table when the INDEX hint is present. This is always possible, as we always have the data PK columns in the index table, and our join optimization would kick in as well.



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