[
https://issues.apache.org/jira/browse/FLINK-14237?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Zili Chen updated FLINK-14237:
------------------------------
Description:
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]
was:
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 cause some confusion to our users who should not
be required to know the detail of Flink 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]
> 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)
