[
https://issues.apache.org/jira/browse/HDDS-631?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16647701#comment-16647701
]
Elek, Marton commented on HDDS-631:
-----------------------------------
Depends from the client application. We have specific ozonefs shaded jar to use
ozonefs, it's enough to use the o3:// hadoop file system.
Also it should be shaded (sooner or later) to make it usable for all the older
hadoop versions, while the jar files used by the services are not shaded.
For rpc clients we have no specific jar file (but ozonefs also good for this)
and 'ozone classpath client' also can be implemented.
> 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]
