[
https://issues.apache.org/jira/browse/PHOENIX-4531?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16328053#comment-16328053
]
Vincent Poon commented on PHOENIX-4531:
---------------------------------------
[~jamestaylor] attached a test "testIndexFailureWithinRSDisablesIndex", can you
take a look and see if it's a valid test? I think if everything's working
correctly, the index should get disabled. Also when I debug, as I step through
I see we don't runOnServer because of this line:
runOnServer &= queryPlans.get(0).getTableRef().getTable().getType() !=
PTableType.INDEX;
> 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: PartialIndexRebuilderIT.java
>
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
