[
https://issues.apache.org/jira/browse/FLINK-22279?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17321846#comment-17321846
]
Yang Wang commented on FLINK-22279:
-----------------------------------
I do not think this is a bug of Flink. The config option
{{pipeline.classpaths}} is designed for working same as CLI option
{{-C,--classpath}}. If you want to ship files, then you should use
{{yarn.ship-files}}.
{code:java}
-C,--classpath <url> Adds a URL to each user code
classloader on all nodes in the
cluster. The paths must specify a
protocol (e.g. file://) and be
accessible on all nodes (e.g. by means
of a NFS share). You can use this
option multiple times for specifying
more than one URL. The protocol must
be supported by the {@link
java.net.URLClassLoader}.
{code}
> Upload the pipeline.classpaths file in yarn application mode
> ------------------------------------------------------------
>
> Key: FLINK-22279
> URL: https://issues.apache.org/jira/browse/FLINK-22279
> Project: Flink
> Issue Type: Bug
> Components: Command Line Client
> Affects Versions: 1.12.0
> Reporter: renjianxu
> Priority: Blocker
>
> pipeline.classpaths is a local resource package. If this file is used, all
> nodes must include this file. I think that pipeline.jars should be uploaded
> from the client.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
