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

Matt Corgan commented on HBASE-5229:
------------------------------------

I think the approach of expanding and improving support for gigantic rows would 
be cleaner than adding another consistency guarantee to hbase's feature list.  
Combining very wide rows with many column families, each with separate settings 
and compactions provides a good framework for all sorts of different data 
models on top.  You could let a row become so big that it's the only row on a 
machine if you want.

>From what I can tell from papers and presentations, BigTable actually supports 
>many gigabyte EntityGroups.  They mention it at 6:18 in this video: 
>http://www.youtube.com/watch?v=xO015C3R6dw .  I'm not sure how "Entity Groups 
>can span machines and still enforce transactionality".  I had thought that an 
>entity group was confined to a single BigTable row, maybe that means they do 
>span BigTable regions.  Anyone know how that works?

                
> 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 somewhere.
> 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

        

Reply via email to