[
https://issues.apache.org/jira/browse/PHOENIX-6045?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17163984#comment-17163984
]
Daniel Wong commented on PHOENIX-6045:
--------------------------------------
With indexes with disjoint set of primary keys I found this. It appears that
while we are considering index plans the both indexes' columns are included in
the projected column list which causes the optimizer to reject the index as the
columns are not covered by either index.
> Delete that should qualify for index path does not use index when multiple
> indexes are available.
> -------------------------------------------------------------------------------------------------
>
> Key: PHOENIX-6045
> URL: https://issues.apache.org/jira/browse/PHOENIX-6045
> Project: Phoenix
> Issue Type: Bug
> Reporter: Daniel Wong
> Priority: Major
> Attachments: MultipleDeleteReproIT.java
>
>
> Delete that should qualify for index path does not use index when multiple
> indexes are available. Test case to reproduce will be below.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
