hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Philip Zeyliger (Commented) (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HBASE-5229) Support atomic region operations
Date Thu, 19 Jan 2012 22:49:41 GMT

    [ https://issues.apache.org/jira/browse/HBASE-5229?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13189456#comment-13189456

Philip Zeyliger commented on HBASE-5229:

Just to kibitz a little bit:

The approach you're proposing will only ever let you do "local" transactions: transactions
clearly related to a prefix-friendly set of rows.  For example, if, say, inserting a tweet
is transactional, but there's a global hash tag index, you might want to make deleting a tweet
transactional in the sense that it'll clean up the index entry for you.  You're never going
to get the index to be on the same region.  It's possible to implement multi-row transactions
on top of single row transactions (by putting a write a head log there, see Megastore at http://research.google.com/pubs/pub36971.html).

On the other hand, if you're cool with that, and even just "local" transactions could be very
useful to many users and is probably quite efficient.  As a user, I'd much prefer dealing
with single rows, or row prefixes, than hoping that my rows are on the same region server.
> Support atomic region operations
> --------------------------------
>                 Key: HBASE-5229
>                 URL: https://issues.apache.org/jira/browse/HBASE-5229
>             Project: HBase
>          Issue Type: New Feature
>          Components: client, regionserver
>            Reporter: Lars Hofhansl
>            Assignee: Lars Hofhansl
>             Fix For: 0.94.0
>         Attachments: 5229.txt
> As discussed (at length) on the dev mailing list with the HBASE-3584 and HBASE-5203 committed,
supporting atomic cross row transactions within a region becomes simple.
> I am aware of the hesitation about the usefulness of this feature, but we have to start
> Let's use this jira for discussion, I'll attach a patch (with tests) momentarily to make
this concrete.

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira


View raw message