[
https://issues.apache.org/jira/browse/HDDS-631?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16760227#comment-16760227
]
Elek, Marton commented on HDDS-631:
-----------------------------------
{quote}Thanks for getting this done, just that if you run this command without
any options, can you please print out all paths, and instruction on how to
modify each one?
{quote}
Not sure if I got it. As of now the command prints out the possible arguments
(names of .classpath files, eg. hadoop-ozone-tools, hadoop-ozone-server-scm) in
case of the argument is missing. I am not sure if it's useful to print out all
the classpath variables (for me each of them are very long).
And it's not intended to be modifiable. You can use HADOOP_CLASSPATH but you
shouldn't modify the .classpath files itself. (only if you are a hadoop
distributor...)
> Ozone classpath shell command is not working
> --------------------------------------------
>
> Key: HDDS-631
> URL: https://issues.apache.org/jira/browse/HDDS-631
> Project: Hadoop Distributed Data Store
> Issue Type: Bug
> Reporter: Nanda kumar
> Assignee: Elek, Marton
> Priority: Blocker
> Attachments: HDDS-631.00.patch, HDDS-631.001.patch
>
>
> In the ozone package (tar) the ozone and its dependency jars are copied to an
> incorrect location. We use to have the jars in {{share/hadoop/<module>}} for
> each module. Those directories are empty now. All the jars are placed in
> {{share/ozone/lib}} directory.
> With this structure when we run {{ozone classpath}} command, we get an
> incorrect output.
> {code}
> $ bin/ozone classpath
> /Users/nvadivelu/apache/ozone-0.4.0-SNAPSHOT/etc/hadoop:/Users/nvadivelu/apache/ozone-0.4.0-SNAPSHOT/share/hadoop/common/*
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: hdfs-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: hdfs-issues-h...@hadoop.apache.org
