[
https://issues.apache.org/jira/browse/PHOENIX-1560?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14279303#comment-14279303
]
Maryann Xue commented on PHOENIX-1560:
--------------------------------------
Got it. Actually if I provide the hint as "INDEX(v vi1)", it will do a scan
over _IDX_IT. So would that be ok?
As to the change in InListExpression, it's a quick fix for an existing bug in
child/parent join optimization. To avoid creating too many objects at runtime,
the LHS expression is a RVC while the RHS expression is a LiteralExpression
evaluated from RVC, and ComparisonExpression.create() will preform rewrite-RVC
which will evaluate the LHS = RHS to a false Boolean.
> 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)
