[
https://issues.apache.org/jira/browse/HBASE-14332?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14722948#comment-14722948
]
Hadoop QA commented on HBASE-14332:
-----------------------------------
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12753224/HBASE-14332_v3.patch
against master branch at commit df341c4299ea21e4e1ca09652f6126633f2307c5.
ATTACHMENT ID: 12753224
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:red}-1 tests included{color}. 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.
{color:red}-1 javac{color}. The patch appears to cause mvn compile goal to
fail with Hadoop version 2.4.0.
Compilation errors resume:
[ERROR] Error invoking method 'get(java.lang.Integer)' in
java.util.ArrayList at META-INF/LICENSE.vm[line 1619, column 22]
[ERROR] Failed to execute goal
org.apache.maven.plugins:maven-remote-resources-plugin:1.5:process (default) on
project hbase-assembly: Error rendering velocity resource. Error invoking
method 'get(java.lang.Integer)' in java.util.ArrayList at
META-INF/LICENSE.vm[line 1619, column 22]: InvocationTargetException: Index: 0,
Size: 0 -> [Help 1]
[ERROR]
[ERROR] To see the full stack trace of the errors, re-run Maven with the -e
switch.
[ERROR] Re-run Maven using the -X switch to enable full debug logging.
[ERROR]
[ERROR] For more information about the errors and possible solutions, please
read the following articles:
[ERROR] [Help 1]
http://cwiki.apache.org/confluence/display/MAVEN/MojoExecutionException
[ERROR]
[ERROR] After correcting the problems, you can resume the build with the command
[ERROR] mvn <goals> -rf :hbase-assembly
Console output:
https://builds.apache.org/job/PreCommit-HBASE-Build/15332//console
This message is automatically generated.
> Show the table state when we encounter exception while disabling / enabling
> table
> ---------------------------------------------------------------------------------
>
> Key: HBASE-14332
> URL: https://issues.apache.org/jira/browse/HBASE-14332
> Project: HBase
> Issue Type: Improvement
> Affects Versions: 2.0.0
> Reporter: Nick.han
> Assignee: Nick.han
> Priority: Minor
> Fix For: 2.0.0
>
> Attachments: HBASE-14332.patch, HBASE-14332_v2.patch,
> HBASE-14332_v3.patch
>
>
> This patch is a advice for good user experience
> reason:
> When we disable a table and the table is not enabled,we receive a
> exception,but the exception is too brief,some time we want to know what
> state is the table in,so that we can know why the table can't be disable.For
> example,I once encountered a problem the table is neither disable nor enable
> when my region server crash down,if we give the table state,I will find the
> problem more quickly .
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
