[ https://issues.apache.org/jira/browse/HDDS-631?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16760235#comment-16760235 ]
Anu Engineer commented on HDDS-631: ----------------------------------- bq. I am not sure if it's useful to print out all the classpath variables (for me each of them are very long). Makes sense, I was thinking it would be a better user interface it printed by default. I see your point, if those strings are too long, it is better to print them one by one. Please go ahead, +1. > 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