[
https://issues.apache.org/jira/browse/HBASE-5229?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13190285#comment-13190285
]
Lars Hofhansl commented on HBASE-5229:
--------------------------------------
@Daniel: Except for RegionCoprocessorEnvironment there are not too many points
there directly expose regions. So I think Todd's point still holds :)
J-D brought to my attention that via scanner batching we can already control
how many columns a scanner.next() call returns. So what I am exploring now is
better control over where to start a scan (allow a column prefix to specified
along with the startRow - the only sticky point is that family delete marker
would not be honored in that case, as we'd want to seek directly to the column
and not seek to the family delete marker first as that would defeat the purpose
completely).
> 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
