hbase-issues mailing list archives

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

     [ https://issues.apache.org/jira/browse/HBASE-5229?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Lars Hofhansl updated HBASE-5229:
---------------------------------

    Attachment: 5229-scanner-seekto.txt

Here's a patch *demonstrating* that approach.
A scanner can be passed a start KeyValue. It will seek to that KeyValue.
The client is responsible to create a suitable KeyValue for seeking (see the included test).
Together with scanner batching this allows for pretty flexible intra row scanning.

For simplicity the stopRow is also enforced allowing only intra-row scanning (that is just
so that the change it ClientScanner is small - otherwise it'd need to remember the seekTo
for retry but still allow to scan to the next region by setting the startRow).

If folks like this approach, I'll make a nicer patch and change the title of this jira.

                
> 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-scanner-seekto.txt, 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

        

Mime
View raw message