[
https://issues.apache.org/jira/browse/FLINK-5236?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15987052#comment-15987052
]
Andrew Roberts edited comment on FLINK-5236 at 4/27/17 5:10 PM:
----------------------------------------------------------------
If the user jar includes a conflicting non-compatible version of some library,
it will break flink with runtime failures if the user-jar comes first. Are you
sure that this is the behavior you want?
was (Author: arobe...@fuze.com):
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)
