[
https://issues.apache.org/jira/browse/FLINK-14237?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16946565#comment-16946565
]
Zili Chen commented on FLINK-14237:
-----------------------------------
Hi [~trohrmann],
{{flink.jar}} is shipped as flink jar on both JM and TM. All usage just happens
to be hardcoded.
On TM part, we actually configure the name via
{{YarnConfigKeys.FLINK_JAR_PATH}}.
On JM part, we happens to hardcode the name as {{flink.jar}} and add it to JM
classpath.
A nit pull request can let JM respect the real name of flink uber jar.
> No need to rename shipped Flink jar
> -----------------------------------
>
> Key: FLINK-14237
> URL: https://issues.apache.org/jira/browse/FLINK-14237
> Project: Flink
> Issue Type: Improvement
> Components: Deployment / YARN
> Reporter: Zili Chen
> Assignee: Zili Chen
> Priority: Major
> Fix For: 1.10.0
>
>
> Currently, when we ship Flink jar configured by -yj, we always rename it as
> {{flink.jar}}. It seems a redundant operation since we can always use the
> exact name of the real jar. It also causes some confusion to our users who
> should not be required to know about Flink internal implementation that they
> configure a specific Flink jar(said {{flink-private-version-suffix.jar}}) but
> cannot find it on YARN container, because it is now {{flink.jar}}.
> CC [~trohrmann]
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
