[
https://issues.apache.org/jira/browse/FLINK-1789?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14906395#comment-14906395
]
ASF GitHub Bot commented on FLINK-1789:
---------------------------------------
Github user mxm commented on the pull request:
https://github.com/apache/flink/pull/593#issuecomment-142943052
I just had a look at this pull request. Why don't we treat the JARs in the
given folder like the the other jar files that are submitted to the cluster via
the BlobManager as part of the job submission? This assumes that the Client can
access the JARs but that's IMHO a fair assumption to make. If the Client can't
access one of the provided JAR files, we can fail with an appropriate error
message.
> Allow adding of URLs to the usercode class loader
> -------------------------------------------------
>
> Key: FLINK-1789
> URL: https://issues.apache.org/jira/browse/FLINK-1789
> Project: Flink
> Issue Type: Improvement
> Components: Distributed Runtime
> Reporter: Timo Walther
> Assignee: Timo Walther
> Priority: Minor
>
> Currently, there is no option to add customs classpath URLs to the
> FlinkUserCodeClassLoader. JARs always need to be shipped to the cluster even
> if they are already present on all nodes.
> It would be great if RemoteEnvironment also accepts valid classpaths URLs and
> forwards them to BlobLibraryCacheManager.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
