phoenix-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Maryann Xue (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (PHOENIX-1560) Join between global index and data table if INDEX hint used
Date Thu, 15 Jan 2015 21:49:34 GMT

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

Maryann Xue commented on PHOENIX-1560:
--------------------------------------

Although adding "NO_DISTINCT_FOR_SEMI_JOIN" would require some change in semi-join runtime,
I assume it's much easier than providing a complete fix for PHOENIX-1589.

> 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, 1560.v2.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)

Mime
View raw message