[
https://issues.apache.org/jira/browse/PHOENIX-6000?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17157037#comment-17157037
]
Lars Hofhansl edited comment on PHOENIX-6000 at 7/13/20, 11:42 PM:
-------------------------------------------------------------------
-v2 contains a test. Sets up two indexes (one global and client side) and an
uncovered local index. Then deletes via the local index and makes the rows are
removed from the local index.
Please have a look.
was (Author: lhofhansl):
-v2 contains a set. Sets up two indexes (one global and client side) and an
uncovered local index. Then deletes via the local index and makes the rows are
removed from the local index.
Please have a look.
> Client side DELETEs should use local indexes for filtering
> ----------------------------------------------------------
>
> Key: PHOENIX-6000
> URL: https://issues.apache.org/jira/browse/PHOENIX-6000
> Project: Phoenix
> Issue Type: Bug
> Reporter: Lars Hofhansl
> Priority: Major
> Attachments: 6000-4.x-HBase-1.5-v2.txt, 6000-4.x-HBase-1.5.txt
>
>
> I just noticed that client side DELETEs do not use local indexes for
> filtering if they do not cover all keys of all other indexes.
> Unless I am missing something this is not necessary, for local indexes we
> have the data available in the region and can fill back the uncovered column
> (just like we do for SELECTs)
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
