You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ozone.apache.org by "Siddharth Wagle (Jira)" <ji...@apache.org> on 2020/01/28 19:40:00 UTC
[jira] [Updated] (HDDS-2218) Use OZONE_CLASSPATH instead of
HADOOP_CLASSPATH
[ https://issues.apache.org/jira/browse/HDDS-2218?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Siddharth Wagle updated HDDS-2218:
----------------------------------
Labels: newbie (was: newbe)
> Use OZONE_CLASSPATH instead of HADOOP_CLASSPATH
> -----------------------------------------------
>
> Key: HDDS-2218
> URL: https://issues.apache.org/jira/browse/HDDS-2218
> Project: Hadoop Distributed Data Store
> Issue Type: Task
> Components: docker
> Reporter: Marton Elek
> Assignee: Sandeep Nemuri
> Priority: Major
> Labels: newbie
>
> HADOOP_CLASSPATH is the standard way to add additional jar files to the classpath of the mapreduce/spark/.. .jobs. If something is added to the HADOOP_CLASSPATH, than it should be on the classpath of the classic hadoop daemons.
> But for the Ozone components we don't need any new jar files (cloud connectors, libraries). I think it's more safe to separated HADOOP_CLASSPATH from OZONE_CLASSPATH. If something is really need on the classpath for Ozone daemons the dedicated environment variable should be used.
>
> Most probably it can be fixed in
> hadoop-hdds/common/src/main/bin/hadoop-functions.sh
> And the hadoop-ozone/dev/src/main/compose files also should be checked (some of them contain HADOOP_CLASSPATH
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: ozone-issues-unsubscribe@hadoop.apache.org
For additional commands, e-mail: ozone-issues-help@hadoop.apache.org