[
https://issues.apache.org/jira/browse/PHOENIX-4531?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16329123#comment-16329123
]
James Taylor commented on PHOENIX-4531:
---------------------------------------
There is an issue. If the delete is being driven from a mutable index, it looks
like we're sending the mutations for both the table and the index. Would you
mind trying my patch, [~vincentpoon]?
As far as runOnServer, we initialize it to false if the table has immutable
indexes here:
{code}
boolean runOnServer = isAutoCommit && !hasPreOrPostProcessing &&
!table.isTransactional() && !hasImmutableIndexes;
{code}
Are you seeing runOnServer as true when there are immutable indexes?
> 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
> Attachments: PHOENIX-4531.v1.master.patch, PHOENIX-4531_v1.patch,
> PartialIndexRebuilderIT.java
>
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
