hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "stack (Updated) (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (HBASE-4854) it seems that CLASSPATH elements coming from Hadoop change HBase behaviour
Date Wed, 23 Nov 2011 05:12:39 GMT

     [ 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

        

Mime
View raw message