[
https://issues.apache.org/jira/browse/FLINK-16005?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17040159#comment-17040159
]
Till Rohrmann commented on FLINK-16005:
---------------------------------------
I think introducing a general way to replace yarn configuration values via
matching prefixes as [~fly_in_gis] proposed, sounds good to me. The only
question I have is whether {{yarn.config}} is a good prefix. The key
{{yarn.config.yarn.application.classpath}} looks a bit weird. It is a bit
unfortunate that the Yarn config key starts with {{yarn}}, otherwise one could
have used this. One could follow Spark's solution and use {{flink.hadoop.}} or
even only {{hadoop.}} as the configuration prefix.
Alternatively, we could also say that we detect prefixes but do not remove
them. That way we could specify {{yarn.application.classpath}} directly in the
configuration or via dynamic program properties.
> Propagate yarn.application.classpath from client to TaskManager Classpath
> -------------------------------------------------------------------------
>
> Key: FLINK-16005
> URL: https://issues.apache.org/jira/browse/FLINK-16005
> Project: Flink
> Issue Type: Improvement
> Components: Deployment / YARN
> Reporter: Zhenqiu Huang
> Priority: Major
>
> When Flink users want to override the hadoop yarn container classpath, they
> should just specify the yarn.application.classpath in yarn-site.xml from cli
> side. But currently, the classpath setting can only be used in flink
> application master, the classpath of TM is still determined by the setting in
> yarn host.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
