[
https://issues.apache.org/jira/browse/HBASE-9097?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13791863#comment-13791863
]
Gary Helmling commented on HBASE-9097:
--------------------------------------
I agree that we should ask the YCSB packaging to be fixed. But I also think
that there will be plenty of other cases where this will come up.
How do we ultimately want HBASE_CLASSPATH to work? Do we want to take the
stance that the "new" behavior is how it should work and you have to fix
anything broken by that? Or do we want to allow an option to use the "new"
behavior, while preserving the "old" behavior as the default (or even vice
versa)? I personally don't have a stake in that I know enough not to be bitten
by this. But if it makes things not work for new users trying to use HBase in
ways that were previously documented, I think that reflects badly on us.
Prior to 0.94.11, we have many releases with the "old" behavior, so if it was
acceptable to change to the "new" behavior in a minor release, I don't think it
should be any less acceptable to change to the "old" behavior now.
> 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)
