[
https://issues.apache.org/jira/browse/HBASE-6776?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13455464#comment-13455464
]
Hadoop QA commented on HBASE-6776:
----------------------------------
-1 overall. Here are the results of testing the latest attachment
http://issues.apache.org/jira/secure/attachment/12545063/trunk-6776.patch
against trunk revision .
+1 @author. The patch does not contain any @author tags.
-1 tests included. The patch doesn't appear to include any new or modified
tests.
Please justify why no new tests are needed for this
patch.
Also please list what manual steps were performed to
verify this patch.
+1 hadoop2.0. The patch compiles against the hadoop 2.0 profile.
+1 javadoc. The javadoc tool did not generate any warning messages.
-1 javac. The patch appears to cause mvn compile goal to fail.
-1 findbugs. The patch appears to cause Findbugs (version 1.3.9) to fail.
+1 release audit. The applied patch does not increase the total number of
release audit warnings.
-1 core tests. The patch failed these unit tests:
Test results:
https://builds.apache.org/job/PreCommit-HBASE-Build/2861//testReport/
Console output:
https://builds.apache.org/job/PreCommit-HBASE-Build/2861//console
This message is automatically generated.
> Opened region of disabled/enabling table is not added to online region list
> ---------------------------------------------------------------------------
>
> Key: HBASE-6776
> URL: https://issues.apache.org/jira/browse/HBASE-6776
> Project: HBase
> Issue Type: Bug
> Reporter: Jimmy Xiang
> Assignee: Jimmy Xiang
> Attachments: trunk-6776.patch
>
>
> For opened region of disabled table, it should be added to online region
> list, and then closed. We should not just ignore them.
> For opened region of enabling table, it should be added to online region
> list, so that we don't have to assign it again. Without adding it to online
> region list, it could be double assigned when assign it again later.
--
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
