[
https://issues.apache.org/jira/browse/TEZ-3734?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16025804#comment-16025804
]
Harish Jaiprakash commented on TEZ-3734:
----------------------------------------
Making sure all configs are used correctly with a test would be hard. Since,
one can start using an existing config in a new I/O but will not get flagged as
it would be covered in another I/O.
Another way could be to wrap config into another config object which takes
whitelisted runtime configs and throws an exception if a runtime config outside
the whitelist is accessed from the I/O. This will ensure that the first time
the config is tested either manually or through a test, the whitelisting is
enforced or it fails. I can make this change if it sounds reasonable.
> Remove config checks in Input/Output.
> -------------------------------------
>
> Key: TEZ-3734
> URL: https://issues.apache.org/jira/browse/TEZ-3734
> Project: Apache Tez
> Issue Type: Bug
> Reporter: Harish Jaiprakash
> Assignee: Harish Jaiprakash
> Attachments: TEZ-3734.01.patch
>
>
> The configs in TezRuntimeConfiguration are not propagated if its not in
> Input/Output checks, remove the checks and propagate all of
> TezRuntimConfiguration to I/Os.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
