[
https://issues.apache.org/jira/browse/PHOENIX-1560?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
James Taylor updated PHOENIX-1560:
----------------------------------
Description: 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. (was: 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.
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.)
> 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
>
> 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)
