phoenix-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "James Taylor (JIRA)" <>
Subject [jira] [Commented] (PHOENIX-1126) Make local index updates transactional with the data updates
Date Wed, 08 Apr 2015 17:59:12 GMT


James Taylor commented on PHOENIX-1126:

bq. Where is the refactor of local index so they are a column family inside the data region?
That would be best way to get transactional updates IMO.
I agree with this. This JIRA would be a stopgap until that work is complete and would only
make sense IMHO if 1) it doesn't require any funky/controversial HBase changes, and 2) it's
easy. The reason I'm exploring this is because we're interested initially in having transactions
for data rows plus their index updates. It's difficult for a client to reason over the state
of the data when you put secondary indexes in the mix under failure scenarios. If this JIRA
is easy and can get us there immediately (it's my understand that Rajeshbabu has already implemented
this in his HIndex implementation), this might be a good interim solution.

> Make local index updates transactional with the data updates
> ------------------------------------------------------------
>                 Key: PHOENIX-1126
>                 URL:
>             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

View raw message