[ https://issues.apache.org/jira/browse/HADOOP-12747?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Sangjin Lee updated HADOOP-12747: --------------------------------- Attachment: HADOOP-12747.01.patch Posted patch v.1. I tested it with a pseudo-distributed cluster. It takes a pretty minimal approach. When it sees a wildcard in the libjars option value, it replaces it with jars in that directory and sets it onto tmpjars. I refactored {{FileUtil}}, {{ApplicationClassLoader}}, and {{GenericOptionsParser}} to use the common implementation (the one that was in {{FileUtil}}). I also updated {{TestGenericOptionsParser}} to use JUnit 4. I would greatly appreciate your review. 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 > > > 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)