[
https://issues.apache.org/jira/browse/TEZ-3734?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16030049#comment-16030049
]
Siddharth Seth commented on TEZ-3734:
-------------------------------------
bq. 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.
Was thinking of this as a heuristic. Nothing is per IO. Assume the current
state is good, and everything has been added to the correct IOs.
If a new config is added to TezRuntimeConfiguration (common to all IOs), a test
would fail - and provide a failure message to add the properties to the correct
place. Kind of twisted, but fairly simple.
bq. 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.
How would this work?
IAC, should we now use this jira for the overall IO fixes, and create a new one
to fix the original intent of adding the few extra properties to relevant IOs?
> 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)
