[
https://issues.apache.org/jira/browse/HADOOP-12747?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15359859#comment-15359859
]
Sangjin Lee commented on HADOOP-12747:
--------------------------------------
For some reason, jenkins didn't post the results. It's here:
https://builds.apache.org/job/PreCommit-HADOOP-Build/9917/console
The unit test failure is the only -1 on the result, and it is unrelated to this
patch. Checkstyle is -0 because a unit test class that I touched is lacking
javadoc at the class level. I think it is OK to not worry about that one.
Regarding the javadoc issue you mentioned Daniel, jenkins returned +1 because
javadoc for private methods/fields is not required and they don't generate
warnings. It is more for information. Would you prefer that I fix them still?
Let me know... Thanks!
> 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, HADOOP-12747.04.patch, HADOOP-12747.05.patch,
> HADOOP-12747.06.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)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
