[
https://issues.apache.org/jira/browse/HDDS-631?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16647570#comment-16647570
]
Nanda kumar commented on HDDS-631:
----------------------------------
If we are not supporting {{ozone classpath}} command, we have to remove it.
bq. We have ozone scm classpath, ozone om classpath
This sounds good, but what if someone wants to run a client application and
they want to use the dependency jars provided by us?
In many cases people would just install/extract the hadoop/ozone tar in edge
node (client installation) and try to run applications by adding it to
classpath.
We have to properly define the directory structure of our installation and
where to find the jars / library 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: [email protected]
For additional commands, e-mail: [email protected]
