[
https://issues.apache.org/jira/browse/PHOENIX-1126?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14084286#comment-14084286
]
James Taylor commented on PHOENIX-1126:
---------------------------------------
IHMO, this is not super important, but more of a nice to have. The reason is
that any time the client commits a batch contains rows that live on more than
one region server, it doesn't help. Real transactions will solve this, so best
IMO to wait until this comes along to solve it completely.
> Make local index updates transactional with the data updates
> ------------------------------------------------------------
>
> Key: PHOENIX-1126
> URL: https://issues.apache.org/jira/browse/PHOENIX-1126
> Project: Phoenix
> Issue Type: Sub-task
> Reporter: James Taylor
> Assignee: rajeshbabu
>
> Given that local index updates happen on the same region server as the data
> updates, we should be able to make them transaction: either both the data and
> index updates succeed, or neither of them do. I seem to remember [~lhofhansl]
> mentioned that the all or none behavior of HRegion.mutateRowsWithLocks()
> could be emulated across tables if you knew that the mutations were all local.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
