[
https://issues.apache.org/jira/browse/HADOOP-12747?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15143798#comment-15143798
]
Sangjin Lee commented on HADOOP-12747:
--------------------------------------
This is a question for [~cnauroth] (or anyone who's intimately familiar with
how we support the libjars argument). You mentioned earlier that libjars don't
support non-local paths, but strictly speaking HADOOP-7112 addresses only the
aspect of adding libjars back to the client classpath. And I know for a fact
today one can use hdfs URLs in libjars successfully (minus putting them in the
client classpath). Is it an accidental behavior while the official position is
that we don't support them? If we do support them in libjars, then we probably
need to support wildcards for them as well. Any feedback is greatly appreciated.
> support wildcard in libjars argument
> ------------------------------------
>
> Key: HADOOP-12747
> URL: https://issues.apache.org/jira/browse/HADOOP-12747
> Project: Hadoop Common
> Issue Type: New Feature
> Components: util
> Reporter: Sangjin Lee
> Assignee: Sangjin Lee
> Attachments: HADOOP-12747.01.patch, HADOOP-12747.02.patch,
> HADOOP-12747.03.patch
>
>
> There is a problem when a user job adds too many dependency jars in their
> command line. The HADOOP_CLASSPATH part can be addressed, including using
> wildcards (\*). But the same cannot be done with the -libjars argument. Today
> it takes only fully specified file paths.
> We may want to consider supporting wildcards as a way to help users in this
> situation. The idea is to handle it the same way the JVM does it: \* expands
> to the list of jars in that directory. It does not traverse into any child
> directory.
> Also, it probably would be a good idea to do it only for libjars (i.e. don't
> do it for -files and -archives).
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
