Return-Path: X-Original-To: apmail-hbase-issues-archive@www.apache.org Delivered-To: apmail-hbase-issues-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id DCB459A8B for ; Sat, 17 Dec 2011 00:03:02 +0000 (UTC) Received: (qmail 88717 invoked by uid 500); 17 Dec 2011 00:03:02 -0000 Delivered-To: apmail-hbase-issues-archive@hbase.apache.org Received: (qmail 88696 invoked by uid 500); 17 Dec 2011 00:03:02 -0000 Mailing-List: contact issues-help@hbase.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Delivered-To: mailing list issues@hbase.apache.org Received: (qmail 88680 invoked by uid 99); 17 Dec 2011 00:03:02 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Sat, 17 Dec 2011 00:03:02 +0000 X-ASF-Spam-Status: No, hits=-2001.5 required=5.0 tests=ALL_TRUSTED,RP_MATCHES_RCVD X-Spam-Check-By: apache.org Received: from [140.211.11.116] (HELO hel.zones.apache.org) (140.211.11.116) by apache.org (qpsmtpd/0.29) with ESMTP; Sat, 17 Dec 2011 00:02:52 +0000 Received: from hel.zones.apache.org (hel.zones.apache.org [140.211.11.116]) by hel.zones.apache.org (Postfix) with ESMTP id 07359119AC1 for ; Sat, 17 Dec 2011 00:02:31 +0000 (UTC) Date: Sat, 17 Dec 2011 00:02:31 +0000 (UTC) From: "Hadoop QA (Commented) (JIRA)" To: issues@hbase.apache.org Message-ID: <720221032.21368.1324080151031.JavaMail.tomcat@hel.zones.apache.org> In-Reply-To: <658178465.20540.1324066110630.JavaMail.tomcat@hel.zones.apache.org> Subject: [jira] [Commented] (HBASE-5058) Allow HBaseAmin to use an existing connection MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 X-Virus-Checked: Checked by ClamAV on apache.org [ https://issues.apache.org/jira/browse/HBASE-5058?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13171323#comment-13171323 ] Hadoop QA commented on HBASE-5058: ---------------------------------- -1 overall. Here are the results of testing the latest attachment http://issues.apache.org/jira/secure/attachment/12507730/5058.txt 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 javadoc. The javadoc tool appears to have generated -152 warning messages. +1 javac. The applied patch does not increase the total number of javac compiler warnings. -1 findbugs. The patch appears to introduce 76 new Findbugs (version 1.3.9) warnings. +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: org.apache.hadoop.hbase.replication.TestReplication org.apache.hadoop.hbase.master.TestMasterRestartAfterDisablingTable Test results: https://builds.apache.org/job/PreCommit-HBASE-Build/526//testReport/ Findbugs warnings: https://builds.apache.org/job/PreCommit-HBASE-Build/526//artifact/trunk/patchprocess/newPatchFindbugsWarnings.html Console output: https://builds.apache.org/job/PreCommit-HBASE-Build/526//console This message is automatically generated. > Allow HBaseAmin to use an existing connection > --------------------------------------------- > > Key: HBASE-5058 > URL: https://issues.apache.org/jira/browse/HBASE-5058 > Project: HBase > Issue Type: Sub-task > Components: client > Affects Versions: 0.94.0 > Reporter: Lars Hofhansl > Assignee: Lars Hofhansl > Priority: Minor > Fix For: 0.94.0 > > Attachments: 5058.txt > > > What HBASE-4805 does for HTables, this should do for HBaseAdmin. > Along with this the shared error handling and retrying between HBaseAdmin and HConnectionManager can also be improved. I'll attach a first pass patch soon. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira