[
https://issues.apache.org/jira/browse/PHOENIX-1126?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14281234#comment-14281234
]
James Taylor commented on PHOENIX-1126:
---------------------------------------
This would be good to revive, [~rajeshbabu], as in the Phoenix/HBase powwow,
[~lhofhansl] made a good point - doing this will provide row level
transactionality for indexes at a low cost. Plus, we have local indexes for
immutable indexes which may be an interesting option for us at Salesforce with
our initial use cases. Would it be feasible to take a similar approach for
local index maintenance in Phoenix as described above?
> 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)
