You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@flink.apache.org by "Andrew Roberts (JIRA)" <ji...@apache.org> on 2017/04/27 17:10:04 UTC
[jira] [Commented] (FLINK-5236) User jar classpath should come
first in classpath
[ https://issues.apache.org/jira/browse/FLINK-5236?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15987052#comment-15987052 ]
Andrew Roberts commented on FLINK-5236:
---------------------------------------
If the user jar loads a conflicting non-compatible version, it will break flink with runtime failures if the user-jar comes first. Are you sure that this is the behavior you want?
> User jar classpath should come first in classpath
> -------------------------------------------------
>
> Key: FLINK-5236
> URL: https://issues.apache.org/jira/browse/FLINK-5236
> Project: Flink
> Issue Type: Bug
> Components: Startup Shell Scripts
> Reporter: Maximilian Michels
> Assignee: Maximilian Michels
>
> The user jar is not part of the classpath set by the startup scripts. We should consider adding it as a first entry in the classpath to avoid that Flink code or Hadoop code loads conflicting versions of a dependency before the user jar is executed.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)