[
https://issues.apache.org/jira/browse/PHOENIX-4531?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
James Taylor updated PHOENIX-4531:
----------------------------------
Fix Version/s: 5.0.0
> 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:
> Reporter: Vincent Poon
> Assignee: Vincent Poon
> Priority: Major
> Fix For: 4.14.0, 5.0.0
>
> Attachments: PHOENIX-4531.v1.master.patch,
> PHOENIX-4531.v3.master.patch, PHOENIX-4531.v4.master.patch,
> PHOENIX-4531.v5.master.patch, PHOENIX-4531_5.x-HBase-2.0.patch,
> PHOENIX-4531_v1.patch, PHOENIX-4531_v2.patch, PartialIndexRebuilderIT.java
>
>
> 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
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
