You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@phoenix.apache.org by "James Taylor (JIRA)" <ji...@apache.org> on 2015/04/08 10:16:12 UTC
[jira] [Commented] (PHOENIX-1126) Make local index updates
transactional with the data updates
[ https://issues.apache.org/jira/browse/PHOENIX-1126?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14484922#comment-14484922 ]
James Taylor commented on PHOENIX-1126:
---------------------------------------
[~rajeshbabu] - wondering if this is feasible to implement for local indexes in Phoenix, as this came up in a talk internally.
> 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.3.4#6332)