[
https://issues.apache.org/jira/browse/HDDS-631?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16648161#comment-16648161
]
Nanda kumar edited comment on HDDS-631 at 1/30/19 8:30 AM:
-----------------------------------------------------------
Sounds good, then we can have different commands to get the classpath.
{{ozone classpath om}}
{{ozone classpath scm}}
{{ozone classpath client}}
Still, we need to have a proper directory structure for the jars.
was (Author: nandakumar131):
Sounds good, then we can have different commands to get the classpath.
{{ozone classpath om}}
{{ozone classpath scm}}
{{ozone classpath clients}}
Still, we need to have a proper directory structure for the jars.
> 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
> Priority: Blocker
> Attachments: HDDS-631.00.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
