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

Posted to issues@flink.apache.org by "Chesnay Schepler (JIRA)" <ji...@apache.org> on 2019/05/24 09:59:00 UTC

[jira] [Commented] (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:comment-tabpanel&focusedCommentId=16847426#comment-16847426 ] 

Chesnay Schepler commented on FLINK-12222:
------------------------------------------

[~zjffdu] What's the state here?

> '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, Scala Shell
>    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 in 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)