[
https://issues.apache.org/jira/browse/TEZ-4141?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17085985#comment-17085985
]
Mustafa Iman commented on TEZ-4141:
-----------------------------------
For container re-use I see it might cause correctness issue.
On the other hand, I don't think there is any correctness issue in LLAP case.
LLAP daemons assume read-only config anyway. LLAP can decide which configs are
not "unsettable" and keep its local config to that set.
Given that, would it be acceptable if reading local configs from disk is a
configurable? LLAP can make use of it, container mode does not have to change
behavior.
> Let Input/Output Processors load local xml configs
> --------------------------------------------------
>
> Key: TEZ-4141
> URL: https://issues.apache.org/jira/browse/TEZ-4141
> Project: Apache Tez
> Issue Type: Improvement
> Reporter: Mustafa Iman
> Assignee: Mustafa Iman
> Priority: Major
> Attachments: TEZ-4141.1.patch
>
>
> We would like to reduce the amount of configuration going over the wire from
> a client to application master. If Input/Output processors load local config
> files, we can reduce the configuration overhead when client and the
> processors have the exact same config on both sides. It is on user of client
> to keep the configs same on both sides. Currently, clients have to send all
> config in payload. Even if we preload config with local xml files, these
> should be overridden by the full config object coming in payload. Therefore,
> old clients that send all the config anyway would not be affected in terms of
> correctness from this change.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
