[
https://issues.apache.org/jira/browse/HBASE-7721?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13595276#comment-13595276
]
Hadoop QA commented on HBASE-7721:
----------------------------------
{color:green}+1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12572417/hbase-7721_v4.patch
against trunk revision .
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:green}+1 tests included{color}. The patch appears to include 21 new
or modified tests.
{color:green}+1 hadoop2.0{color}. The patch compiles against the hadoop
2.0 profile.
{color:green}+1 javadoc{color}. The javadoc tool did not generate any
warning messages.
{color:green}+1 javac{color}. The applied patch does not increase the
total number of javac compiler warnings.
{color:green}+1 findbugs{color}. The patch does not introduce any new
Findbugs (version 1.3.9) warnings.
{color:green}+1 release audit{color}. The applied patch does not increase
the total number of release audit warnings.
{color:green}+1 lineLengths{color}. The patch does not introduce lines
longer than 100
{color:green}+1 core tests{color}. The patch passed unit tests in .
Test results:
https://builds.apache.org/job/PreCommit-HBASE-Build/4700//testReport/
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/4700//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-client.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/4700//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-examples.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/4700//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-protocol.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/4700//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-hadoop1-compat.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/4700//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-prefix-tree.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/4700//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-common.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/4700//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-hadoop-compat.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/4700//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-server.html
Console output:
https://builds.apache.org/job/PreCommit-HBASE-Build/4700//console
This message is automatically generated.
> Atomic multi-row mutations in META
> ----------------------------------
>
> Key: HBASE-7721
> URL: https://issues.apache.org/jira/browse/HBASE-7721
> Project: HBase
> Issue Type: Improvement
> Components: Coprocessors, regionserver
> Reporter: Enis Soztutar
> Assignee: Enis Soztutar
> Fix For: 0.95.0, 0.98.0
>
> Attachments: hbase-7721_v1.patch, hbase-7721_v2.patch,
> hbase-7721_v3.patch, hbase-7721_v4.patch
>
>
> Thanks to Lars' local transactions patch (HBASE-5229), we can entertain the
> possibility of doing local transactions within META regions.
> We need this mainly for region splits and merges. Clients scan the META
> concurrent to the split/merge operations, and to prevent the clients from
> seeing overlapping region boundaries or holes in META, we just through hoops.
> For more backgroun, see BlockingMetaScannerVisitor, HBASE-5986, and my
> comments at https://reviews.apache.org/r/8716/.
> Now, for the actual implementation options:
> 1. As outlined in http://hadoop-hbase.blogspot.com/2012_02_01_archive.html,
> - We have to implement a Custom RegionSplitPolicy for the META regions to
> ensure that a table's regions are always co-located in the same META region.
> Then we can add MultiRowMutationEndpoint as a system level coprocessor, and
> use it for META operations.
> 2. Do smt like HBASE-7716, and expose local atomic multi-row operations as a
> native API.
> 3. Move META to zookeeper. Use zookeeper.multi.
> Then we can change region split / merge logic to make use of atomic META
> operations.
> Thoughts, suggestions?
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
