[
https://issues.apache.org/jira/browse/PHOENIX-6045?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17164774#comment-17164774
]
Daniel Wong commented on PHOENIX-6045:
--------------------------------------
[~larsh] I think [~kozdemir] has a bit more context on this as he was looking
into it in more detail but this is my understanding.
For mutable indexes we don't need the other keys since the delete of the index
rows are powered by the server side, (rather than the client side). For
immutable cases you are correct that if we were powering it from the client we
would need the other index keys to delete from the index rows. I think this
Jira is still valid. What do you think?
> 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
> Affects Versions: 5.0.0, 4.15.0, 4.14.3
> Reporter: Daniel Wong
> Priority: Major
> Fix For: 5.1.0, 4.16.0
>
> 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)
