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 22:26:40 GMT

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

Lars Hofhansl commented on HBASE-5229:

That is true when it comes to storage.
However our (current) API is mostly row based. There is no way to start or stop a stop a scan
at a column, there are many assumptions about rows baked into the scanner, etc. I don't think
ColumnRangeFilter would be good enough here.

Declaring a prefix and honoring it during splitting seems simpler and more in line with our
current API and (probably?) what a user would expect.

It is another avenue, though. For example we can add Scan.set{Start|Stop}Key (where we can
present prefixes of the full key, rather than just the row key), and handle it accordingly
at the server. Would also need a nextKeyValue (or nextColumn or something) method on ResultScanner
along with the server code that does this efficiently.

> 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