[
https://issues.apache.org/jira/browse/PHOENIX-1150?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14088313#comment-14088313
]
James Taylor commented on PHOENIX-1150:
---------------------------------------
Thanks for the patch, [~rajesh23]. Overall looks good, but the changes to
WhereOptimizer aren't necessary IMO. I renamed
KeyExpressionVisitor.DEGENERATE_KEY_PARTS to EMPTY_KEY_SLOTS as the name is
confusing (it doesn't mean the scan will not return anything, it just means
that nothing in the where clause was found to further contribute to the
start/stop row).
I'll go ahead and commit it to fix the tests I broke.
> scan on local index(index of view) for queries with no where condition should
> not read other indexes data stored in the shared index table
> ------------------------------------------------------------------------------------------------------------------------------------------
>
> Key: PHOENIX-1150
> URL: https://issues.apache.org/jira/browse/PHOENIX-1150
> Project: Phoenix
> Issue Type: Bug
> Reporter: rajeshbabu
> Assignee: rajeshbabu
> Fix For: 5.0.0, 4.1
>
> Attachments: PHOENIX-1150.patch
>
>
> Currently covered index queries or queries like count() with no where
> condition choose index table to scan directly.In that case while scanning
> local index or index on view getting other indexes data also. Which will give
> inconsistent results when a table(view) has multiple local(view) indexes. We
> should restrict to scan only the index data.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
