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 A3A587262 for ; Wed, 23 Nov 2011 02:45:04 +0000 (UTC) Received: (qmail 47165 invoked by uid 500); 23 Nov 2011 02:45:04 -0000 Delivered-To: apmail-hbase-issues-archive@hbase.apache.org Received: (qmail 47128 invoked by uid 500); 23 Nov 2011 02:45: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 47116 invoked by uid 99); 23 Nov 2011 02:45:02 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 23 Nov 2011 02:45:02 +0000 X-ASF-Spam-Status: No, hits=-2001.2 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; Wed, 23 Nov 2011 02:45:01 +0000 Received: from hel.zones.apache.org (hel.zones.apache.org [140.211.11.116]) by hel.zones.apache.org (Postfix) with ESMTP id EEDF29855E for ; Wed, 23 Nov 2011 02:44:40 +0000 (UTC) Date: Wed, 23 Nov 2011 02:44:40 +0000 (UTC) From: "Hadoop QA (Commented) (JIRA)" To: issues@hbase.apache.org Message-ID: <299571286.4877.1322016280980.JavaMail.tomcat@hel.zones.apache.org> In-Reply-To: <1473239985.4562.1322006799872.JavaMail.tomcat@hel.zones.apache.org> Subject: [jira] [Commented] (HBASE-4854) it seems that CLASSPATH elements coming from Hadoop change HBase behaviour MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/HBASE-4854?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13155644#comment-13155644 ] Hadoop QA commented on HBASE-4854: ---------------------------------- -1 overall. Here are the results of testing the latest attachment http://issues.apache.org/jira/secure/attachment/12504829/HBASE-4854.patch.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 -162 warning messages. +1 javac. The applied patch does not increase the total number of javac compiler warnings. -1 findbugs. The patch appears to introduce 66 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.client.TestInstantSchemaChange org.apache.hadoop.hbase.client.TestAdmin org.apache.hadoop.hbase.TestRegionRebalancing org.apache.hadoop.hbase.replication.TestReplication Test results: https://builds.apache.org/job/PreCommit-HBASE-Build/340//testReport/ Findbugs warnings: https://builds.apache.org/job/PreCommit-HBASE-Build/340//artifact/trunk/patchprocess/newPatchFindbugsWarnings.html Console output: https://builds.apache.org/job/PreCommit-HBASE-Build/340//console This message is automatically generated. > it seems that CLASSPATH elements coming from Hadoop change HBase behaviour > -------------------------------------------------------------------------- > > Key: HBASE-4854 > URL: https://issues.apache.org/jira/browse/HBASE-4854 > Project: HBase > Issue Type: Bug > Components: shell > Affects Versions: 0.92.0 > Reporter: Roman Shaposhnik > Assignee: Roman Shaposhnik > Attachments: HBASE-4854.patch.txt > > > It looks like HBASE-3465 introduced a slight change in behavior. The ordering of classpath elements makes Hadoop ones go before the HBase ones, which leads to log4j properties picked up from the wrong place, etc. It seems that the easies way to fix that would be to revert the ordering of classpath. -- 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