[
https://issues.apache.org/jira/browse/HDDS-1520?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16842383#comment-16842383
]
Elek, Marton commented on HDDS-1520:
------------------------------------
bq. The solution is to make sure that we can put jar files in a directory, and
use "lib/*" class path wildcards provided short hand to reference all jar files.
I propose to use a different solution instead of the lib/* approach as it
doesn't solve the problems which are discussed in HDDS-447.
I think we can create helper jar files to define relative classpath in the
Manifest (or just use the main artifacts with manifest entries).
> Ozone Classpath does not scale well using long path prefix to OZONE_HOME
> ------------------------------------------------------------------------
>
> Key: HDDS-1520
> URL: https://issues.apache.org/jira/browse/HDDS-1520
> Project: Hadoop Distributed Data Store
> Issue Type: Sub-task
> Reporter: Eric Yang
> Assignee: Elek, Marton
> Priority: Major
>
> [~eyang] reported that the ozone can't be started if the ozone directory is
> symlinked due to the classpath assembly. It should work even if the directory
> is symlinked.
> Ozone script generates CLASSPATH environment variable based on parsing of
> ozone-0.5.0-SNAPSHOT/share/ozone/classpath/*.classpath file, then substitute
> HDDS_LIB_JARS_DIR with OZONE_HOME/share/ozone/lib. When OZONE_HOME directory
> path has a long prefix, this can cause CLASSPATH environment variable to
> exceed string length limit set for a single environment variable. This cause
> Ozone command to return random errors with class not found exception.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
