hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Gary Helmling (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HBASE-9097) Set HBASE_CLASSPATH before rest of the classpath
Date Thu, 10 Oct 2013 18:37:44 GMT

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

Gary Helmling commented on HBASE-9097:
--------------------------------------

{quote}
However, people getting started with HBase often use pre-built YCSB tarball that already has
this fat jar compiled with HBase version 0.90.5, which of course fails to run against newer
versions of HBase. The fact that HBase book (The Definitive Guide) also recommend this strategy
(Chapter 7, pg 297) may lead someone to actually try building an application this way.
{quote}

Fair enough.  I agree it's not a good user experience to break things that were previously
working for people.  I think previously there was a question on whether this would be a problem
in practice, but it looks like that's been answered in the positive.

Want to open a JIRA to add a HBASE_USER_CLASSPATH_FIRST variable or HBASE_CLASSPATH_OVERRIDE
so that HBASE_CLASSPATH can go back to the old behavior?

> Set HBASE_CLASSPATH before rest of the classpath
> ------------------------------------------------
>
>                 Key: HBASE-9097
>                 URL: https://issues.apache.org/jira/browse/HBASE-9097
>             Project: HBase
>          Issue Type: Bug
>          Components: scripts
>    Affects Versions: 0.98.0, 0.95.2, 0.94.11
>            Reporter: Jesse Yates
>            Assignee: Jesse Yates
>             Fix For: 0.98.0, 0.95.2, 0.94.11
>
>         Attachments: hbase-9097-v0.patch
>
>
> We encountered this when one of the hadoop test jars (specifically hadoop-mapreduce-client-jobclient-2.0.0-cdh4.3.0-tests.jar,
but that's beside the point) had an hdfs-site.xml. This clobbered the hdfs-site.xml that we
included on the classpath via HBASE_CLASSPATH in hbase-env.sh, meaning the master didn't start
in HA NN mode, because the proxy-provider wasn't found in the hdfs-site.xml from the test
jar (even though it was in our config file) because that was the first resolution of that
file.
> This should be a fairly simple fix in bin/hbase, but has some potentially wide-ranging
effects on existing installs that just 'happen' to work.
> Generally, I'd expect things set on the HBASE_CLASSPATH to take precedence over anything
else when starting the hbase daemon.



--
This message was sent by Atlassian JIRA
(v6.1#6144)

Mime
View raw message