hbase-issues mailing list archives

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

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

Lars Hofhansl commented on HBASE-5229:

That argument pretty much sinks this approach for me.

At the same time we should not put a full transactional API into HBase, but rather provide
enough building blocks so that an outside client could implement transactions. I do not see
how we can do that without exposing knowledge about some internals such as regions.

Another approach is to give more control over which set of rows can participate in a transaction.
Right now that is all KVs with the same row-key (internally we achieve by collocating all
those KVs, but that is an implementation detail).
What if we allow a prefix of the row key instead? We can even formalize that, and give the
row key some internal (optional) structure, which allows the application to specific transaction
> 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