hadoop-hdfs-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Elek, Marton (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HDDS-631) Ozone classpath shell command is not working
Date Tue, 05 Feb 2019 15:28:00 GMT

    [ https://issues.apache.org/jira/browse/HDDS-631?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16760931#comment-16760931

Elek, Marton commented on HDDS-631:

Thanks [~anu] the review.

The scm classpath in the container is 6873 character which is about 40 lines on my terminal.
and we have 7 classpath definitions as of now:

Usage: ozone classpath <ARTIFACTNAME>
Where the artifact name is one of:


I will commit this patch to fix the classpath command, but let me now if you have further
usability suggestions.

> 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

To unsubscribe, e-mail: hdfs-issues-unsubscribe@hadoop.apache.org
For additional commands, e-mail: hdfs-issues-help@hadoop.apache.org

View raw message