hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hadoop QA (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HBASE-12586) Task 6 & 7 from HBASE-9117, delete all public HTable constructors and delete ConnectionManager#{delete,get}Connection
Date Sat, 07 Mar 2015 01:52:40 GMT

    [ https://issues.apache.org/jira/browse/HBASE-12586?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14351311#comment-14351311

Hadoop QA commented on HBASE-12586:

{color:red}-1 overall{color}.  Here are the results of testing the latest attachment 
  against master branch at commit 95fc53f1056238e0b5f65df7f3015f2aec3d0a20.
  ATTACHMENT ID: 12703199

    {color:green}+1 @author{color}.  The patch does not contain any @author tags.

    {color:green}+1 tests included{color}.  The patch appears to include 27 new or modified

    {color:red}-1 javac{color}.  The patch appears to cause mvn compile goal to fail with
Hadoop version 2.4.1.

    Compilation errors resume:
[ERROR] /home/jenkins/jenkins-slave/workspace/PreCommit-HBASE-Build/hbase-client/src/main/java/org/apache/hadoop/hbase/client/HTableFactory.java:[41,14]
no suitable constructor found for HTable(org.apache.hadoop.conf.Configuration,org.apache.hadoop.hbase.TableName)
[ERROR] Failed to execute goal org.apache.maven.plugins:maven-compiler-plugin:3.2:compile
(default-compile) on project hbase-client: Compilation failure
[ERROR] /home/jenkins/jenkins-slave/workspace/PreCommit-HBASE-Build/hbase-client/src/main/java/org/apache/hadoop/hbase/client/HTableFactory.java:[41,14]
no suitable constructor found for HTable(org.apache.hadoop.conf.Configuration,org.apache.hadoop.hbase.TableName)
[ERROR] constructor org.apache.hadoop.hbase.client.HTable.HTable(org.apache.hadoop.hbase.client.ClusterConnection,org.apache.hadoop.hbase.client.BufferedMutatorParams)
is not applicable
[ERROR] (actual argument org.apache.hadoop.conf.Configuration cannot be converted to org.apache.hadoop.hbase.client.ClusterConnection
by method invocation conversion)
[ERROR] constructor org.apache.hadoop.hbase.client.HTable.HTable(org.apache.hadoop.hbase.TableName,org.apache.hadoop.hbase.client.ClusterConnection,org.apache.hadoop.hbase.client.TableConfiguration,org.apache.hadoop.hbase.client.RpcRetryingCallerFactory,org.apache.hadoop.hbase.ipc.RpcControllerFactory,java.util.concurrent.ExecutorService)
is not applicable
[ERROR] (actual and formal argument lists differ in length)
[ERROR] -> [Help 1]
[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] For more information about the errors and possible solutions, please read the following
[ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/MojoFailureException
[ERROR] After correcting the problems, you can resume the build with the command
[ERROR]   mvn <goals> -rf :hbase-client

Console output: https://builds.apache.org/job/PreCommit-HBASE-Build/13126//console

This message is automatically generated.

> Task 6 & 7 from HBASE-9117,  delete all public HTable constructors and delete ConnectionManager#{delete,get}Connection
> ----------------------------------------------------------------------------------------------------------------------
>                 Key: HBASE-12586
>                 URL: https://issues.apache.org/jira/browse/HBASE-12586
>             Project: HBase
>          Issue Type: Task
>    Affects Versions: 2.0.0
>            Reporter: stack
>            Assignee: Mikhail Antonov
>              Labels: beginner, beginners
>         Attachments: HBASE-12586.patch
> Finish cleanup from HBASE-9117 removing old API.  This issue covers tasks 6 and 7 from
the list here: https://issues.apache.org/jira/browse/HBASE-9117?focusedCommentId=13919716&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-13919716
> To be done in master branch only.
> Marked as beginner task.  The idea is straight-forward.  It is just a lot of work going
through all tests converting to use new API.

This message was sent by Atlassian JIRA

View raw message