You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@flink.apache.org by "Till Rohrmann (JIRA)" <ji...@apache.org> on 2019/05/10 10:02:00 UTC

[jira] [Resolved] (FLINK-12459) YarnConfigOptions#CLASSPATH_INCLUDE_USER_JAR should affect the order of classpath between user jars and flink jars

     [ https://issues.apache.org/jira/browse/FLINK-12459?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Till Rohrmann resolved FLINK-12459.
-----------------------------------
       Resolution: Fixed
    Fix Version/s: 1.9.0

Fixed via c646cb2cb78668285e6d0e8568be4f30ea03fa7d

> YarnConfigOptions#CLASSPATH_INCLUDE_USER_JAR should affect the order of classpath between user jars and flink jars
> ------------------------------------------------------------------------------------------------------------------
>
>                 Key: FLINK-12459
>                 URL: https://issues.apache.org/jira/browse/FLINK-12459
>             Project: Flink
>          Issue Type: Improvement
>          Components: Command Line Client
>            Reporter: Victor Wong
>            Assignee: Victor Wong
>            Priority: Minor
>              Labels: pull-request-available
>             Fix For: 1.9.0
>
>         Attachments: image-2019-05-09-15-04-36-360.png
>
>          Time Spent: 10m
>  Remaining Estimate: 0h
>
> When setting YarnConfigOptions#CLASSPATH_INCLUDE_USER_JAR to "LAST", I think the user jars should come after all flink libs&jars in runtime classpath, including "flink.jar".
> But actually it's not:
> org.apache.flink.yarn.AbstractYarnClusterDescriptor#startAppMaster !image-2019-05-09-15-04-36-360.png!
> I'm not sure if it's an expected behavior, because if a user forgets to mark Flink dependencies as "provided", it causes conflicts in detached mode. 
>  



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)