[
https://issues.apache.org/jira/browse/FLINK-3839?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15327195#comment-15327195
]
Robert Thorman commented on FLINK-3839:
---------------------------------------
I've been working through the debugger on CliFrontend and ProgramOptions and it
does seem to allow the URLClassloader formats up to the point where
PackedProgram.extractCotainedLibraries loads jars into the execution
environment.
So I think there are two options. 1) just extend the -C option to expand
anything ending in a / into a list of jars, or 2) add a -cp option that
establishes a true classpath of resources (jars, libs, etc.).
My preference would be to extend the current -C option and make is process the
URL formats as outlined in the URLClassloader javadocs.
Thoughts?
> Support wildcards in classpath parameters
> -----------------------------------------
>
> Key: FLINK-3839
> URL: https://issues.apache.org/jira/browse/FLINK-3839
> Project: Flink
> Issue Type: Improvement
> Reporter: Ken Krugler
> Assignee: Robert Thorman
> Priority: Minor
>
> Currently you can only specify a single explict jar with the CLI --classpath
> file://<path to jar> parameter.Java (since 1.6) has allowed you to use -cp
> <path to directory>/* as a way of adding every file that ends in .jar in a
> directory.
> This would simplify things, e.g. when running on EMR you have to add roughly
> 120 jars explicitly, but these are all located in just two directories.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
