[
https://issues.apache.org/jira/browse/FLINK-16005?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17040881#comment-17040881
]
Yang Wang commented on FLINK-16005:
-----------------------------------
[~trohrmann]
What i mean is if we override some hadoop keys(core-site.xml, hdfs-site.xml)
in {{YarnConfiguration}} object, i am afraid it could not take effect. For
example, in `YarnClusterDescriptor`, we use {{YarnConfiguration}}, not
{{HdfsConfiguration,}} to get the hadoop {{FileSystem}}. However, i am not very
sure and will check the hadoop code for confirmation.
Also this discussion inspires that some other tickets could be done in the
similar way.
[1]. Allow set file.replication in Yarn Configuration, FLINK-12343
[2]. Make Yarn staging directory configurable, FLINK-15405
> 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)
