[
https://issues.apache.org/jira/browse/FLINK-1789?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14906566#comment-14906566
]
ASF GitHub Bot commented on FLINK-1789:
---------------------------------------
Github user mxm commented on the pull request:
https://github.com/apache/flink/pull/593#issuecomment-142975593
@aalexandrov Concerning the folders, you wrote:
> The idea is to add support for proper *folders* next to jars when opening
an execution environment. Since folders cannot be handled the same way as jars
during execution (i.e., serialize and ship them around by the blob manager),
the assumption for folder paths is that they are accessible from all agents in
the distributed runtime (JobManager + TaskManagers), e.g., via shared NFS
folders.
@StephanEwen Why can't the "dynamically generated" class files not be
shipped during deployment of the job and thereafter be available through the
flink user code classloader?
I didn't see any hint in the JIRA or in this pull request that the classes
should be generated at runtime. So either I don't understand this feature
correctly or the feature description in the JIRA is not correct.
> 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)
