[
https://issues.apache.org/jira/browse/PHOENIX-4531?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16328032#comment-16328032
]
Vincent Poon commented on PHOENIX-4531:
---------------------------------------
This is also problematic because the delete against the index table is issued
first, so if there's something goes wrong with the delete, the entire statement
fails with an exception, and the failure policy is never activated so the index
remains active.
> Delete on a table with a global mutable index can issue client-side deletes
> against the index
> ---------------------------------------------------------------------------------------------
>
> Key: PHOENIX-4531
> URL: https://issues.apache.org/jira/browse/PHOENIX-4531
> Project: Phoenix
> Issue Type: Bug
> Affects Versions: 4.13.0
> Environment: For a table with a global mutable index, I found the
> following result in client-side deletes against both the data table and index
> table.
> "DELETE FROM data_table"
> "DELETE FROM data_table WHERE indexed_col='v'"
> We only need the delete to be issued against the data table, because
> 1) It's redundant since a delete against the index will be issued on the
> server side when we process the delete of the data table row
> 2) Deletes issued from the client-side won't have the index failure policy
> Reporter: Vincent Poon
> Assignee: Vincent Poon
> Priority: Major
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
