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

Posted to issues@flink.apache.org by "Jeff Zhang (JIRA)" <ji...@apache.org> on 2019/04/17 08:07:01 UTC

[jira] [Updated] (FLINK-12222) `start-scala-shell -a ` doesn't ship jars to yarn container

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

Jeff Zhang updated FLINK-12222:
-------------------------------
    Summary: `start-scala-shell -a <jars>` doesn't ship jars to yarn container  (was: No way to ship custom jars to yarn cluster in scala-shell)

> `start-scala-shell -a <jars>` doesn't ship jars to yarn container
> -----------------------------------------------------------------
>
>                 Key: FLINK-12222
>                 URL: https://issues.apache.org/jira/browse/FLINK-12222
>             Project: Flink
>          Issue Type: Bug
>          Components: Deployment / YARN
>    Affects Versions: 1.8.0
>            Reporter: Jeff Zhang
>            Assignee: Jeff Zhang
>            Priority: Major
>
> If user use `flink run` to submit flink jars, he could build uber jar to include all its dependencies, but flink scala-shell, there's no way to ship custom jars.  Currently `start-scala-shell -a <jars>` only put the jars on the classpath of client side, but doesn't ship it to yarn container. This make it impossible to use these jars in flink tasks.



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