You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hbase.apache.org by "Roman Shaposhnik (Created) (JIRA)" <ji...@apache.org> on 2011/11/23 01:06:39 UTC
[jira] [Created] (HBASE-4854) it seems that CLASSPATH elements
coming from Hadoop change HBase behaviour
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
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
[jira] [Commented] (HBASE-4854) it seems that CLASSPATH elements
coming from Hadoop change HBase behaviour
Posted by "Hudson (Commented) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HBASE-4854?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13155824#comment-13155824 ]
Hudson commented on HBASE-4854:
-------------------------------
Integrated in HBase-0.92-security #8 (See [https://builds.apache.org/job/HBase-0.92-security/8/])
HBASE-4854 it seems that CLASSPATH elements coming from Hadoop change HBase behaviour
stack :
Files :
* /hbase/branches/0.92/CHANGES.txt
* /hbase/branches/0.92/bin/hbase
> 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
> Fix For: 0.92.0
>
> 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
[jira] [Updated] (HBASE-4854) it seems that CLASSPATH elements
coming from Hadoop change HBase behaviour
Posted by "stack (Updated) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HBASE-4854?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
stack updated HBASE-4854:
-------------------------
Resolution: Fixed
Fix Version/s: 0.92.0
Hadoop Flags: Reviewed
Status: Resolved (was: Patch Available)
Commmitted branch and trunk. Thanks for patch Roman.
> 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
> Fix For: 0.92.0
>
> 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
[jira] [Commented] (HBASE-4854) it seems that CLASSPATH elements
coming from Hadoop change HBase behaviour
Posted by "Hudson (Commented) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HBASE-4854?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13155868#comment-13155868 ]
Hudson commented on HBASE-4854:
-------------------------------
Integrated in HBase-TRUNK #2474 (See [https://builds.apache.org/job/HBase-TRUNK/2474/])
HBASE-4854 it seems that CLASSPATH elements coming from Hadoop change HBase behaviour
stack :
Files :
* /hbase/trunk/bin/hbase
> 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
> Fix For: 0.92.0
>
> 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
[jira] [Updated] (HBASE-4854) it seems that CLASSPATH elements
coming from Hadoop change HBase behaviour
Posted by "Roman Shaposhnik (Updated) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HBASE-4854?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Roman Shaposhnik updated HBASE-4854:
------------------------------------
Status: Patch Available (was: Open)
> 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
[jira] [Commented] (HBASE-4854) it seems that CLASSPATH elements
coming from Hadoop change HBase behaviour
Posted by "Hadoop QA (Commented) (JIRA)" <ji...@apache.org>.
[ 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
[jira] [Commented] (HBASE-4854) it seems that CLASSPATH elements
coming from Hadoop change HBase behaviour
Posted by "Hudson (Commented) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HBASE-4854?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13155784#comment-13155784 ]
Hudson commented on HBASE-4854:
-------------------------------
Integrated in HBase-TRUNK-security #6 (See [https://builds.apache.org/job/HBase-TRUNK-security/6/])
HBASE-4854 it seems that CLASSPATH elements coming from Hadoop change HBase behaviour
stack :
Files :
* /hbase/trunk/bin/hbase
> 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
> Fix For: 0.92.0
>
> 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
[jira] [Updated] (HBASE-4854) it seems that CLASSPATH elements
coming from Hadoop change HBase behaviour
Posted by "Roman Shaposhnik (Updated) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HBASE-4854?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Roman Shaposhnik updated HBASE-4854:
------------------------------------
Attachment: HBASE-4854.patch.txt
> 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
[jira] [Commented] (HBASE-4854) it seems that CLASSPATH elements
coming from Hadoop change HBase behaviour
Posted by "Hudson (Commented) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HBASE-4854?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13159786#comment-13159786 ]
Hudson commented on HBASE-4854:
-------------------------------
Integrated in HBase-0.92 #163 (See [https://builds.apache.org/job/HBase-0.92/163/])
HBASE-4854 it seems that CLASSPATH elements coming from Hadoop change HBase behaviour
stack :
Files :
* /hbase/branches/0.92/CHANGES.txt
* /hbase/branches/0.92/bin/hbase
> 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
> Fix For: 0.92.0
>
> 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