[ 
https://issues.apache.org/jira/browse/FLINK-1789?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14492515#comment-14492515
 ] 

ASF GitHub Bot commented on FLINK-1789:
---------------------------------------

GitHub user twalthr opened a pull request:

    https://github.com/apache/flink/pull/593

    [FLINK-1789] [core] [runtime] [java-api] Allow adding of URLs to the 
usercode class loader

    See [FLINK-1789].
    
    I was a little bit unsure in `JobWithJars` because it is not guaranteed 
that the classpath is correct locally, maybe someone can have a look at it.

You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/twalthr/flink CustomUrlsToUserClassloader

Alternatively you can review and apply these changes as the patch at:

    https://github.com/apache/flink/pull/593.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

    This closes #593
    
----
commit 1f45400fb0bfa3388b5f641cc700a6f15bc40678
Author: twalthr <[email protected]>
Date:   2015-04-08T23:33:40Z

    [FLINK-1789] [core] [runtime] [java-api] Allow adding of URLs to the 
usercode class loader

----


> 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)

Reply via email to