[
https://issues.apache.org/jira/browse/HBASE-7315?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13557904#comment-13557904
]
Hadoop QA commented on HBASE-7315:
----------------------------------
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12565620/HBASE-7315-v7.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 88 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:red}-1 findbugs{color}. The patch appears to cause Findbugs
(version 1.3.9) to fail.
{color:green}+1 release audit{color}. The applied patch does not increase
the total number of release audit warnings.
{color:red}-1 lineLengths{color}. The patch introduces 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/4098//testReport/
Console output:
https://builds.apache.org/job/PreCommit-HBASE-Build/4098//console
This message is automatically generated.
> Remove support for client-side RowLocks
> ---------------------------------------
>
> Key: HBASE-7315
> URL: https://issues.apache.org/jira/browse/HBASE-7315
> Project: HBase
> Issue Type: Sub-task
> Components: Transactions/MVCC
> Reporter: Gregory Chanan
> Assignee: Gregory Chanan
> Priority: Critical
> Fix For: 0.96.0
>
> Attachments: HBASE-7315.patch, HBASE-7315-v2.patch,
> HBASE-7315-v3.patch, HBASE-7315-v4.patch, HBASE-7315-v5.patch,
> HBASE-7315-v6.patch, HBASE-7315-v7.patch
>
>
> See comments in HBASE-7263.
--
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
