[
https://issues.apache.org/jira/browse/PHOENIX-1126?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14485758#comment-14485758
]
James Taylor commented on PHOENIX-1126:
---------------------------------------
Agreed - just exploring right now, [~stack]. I think we agree on the end goal.
Seems like we have a few choices:
1. focus solely on column family inside the data region for local indexes and
deprecate the other local index implementation. I imagine this is a 1.1 only
feature and I don't know what the expected release date is for this. What if
our existing local index implementation cannot be maintained as it's still on
unsupported APIs (see (2) below). Also, it's not clear to me what the level of
effort is for this new local index implementation.
2. do (1), but first get local indexes on the new supported APIs so we don't
break existing customers already using local indexing as new HBase versions are
rolled out.
3. implement this JIRA as stopgap so that we have a reasonable transactional
story (which is one of the big potential benefits of local indexes).
4. don't implement this JIRA but rely on our broader transaction support (which
is in the works). The performance of this broader transaction support is
currently unknown, so this JIRA hedges our bets.
> 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)
