[
https://issues.apache.org/jira/browse/PHOENIX-6045?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17165986#comment-17165986
]
Daniel Wong edited comment on PHOENIX-6045 at 7/27/20, 10:24 PM:
-----------------------------------------------------------------
[~larsh] thats essentially what I was mentioning but I did not communicate it
properly.
I was suggesting for mutable tables that we could select from index1 the PKs
and use that to generate mutation state for the base table which any index by
definition has. We could then send mutations to the base table. As part of
the mutation once we delete from the base table the deletions could propagate
to both index1 and index2. Either through readback as you are mentioning or can
the server propgate the mutations? If the index select is much more efficient
this overall process could be more efficient?
was (Author: dbwong):
[~larsh] thats essentially what I was mentioning but I did not communicate it
properly.
I was suggesting for mutable tables that we could select from index1 the PKs
and use that to generate mutation state for the base table which any index by
definition has. We could then send mutations to the base table. As part of
the mutation once we delete from the base table the deletions could propagate
to both index1 and index2. If the index select is much more efficient this
overall process could be more efficient?
> 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)
