[
https://issues.apache.org/jira/browse/TEZ-3734?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16025421#comment-16025421
]
Siddharth Seth commented on TEZ-3734:
-------------------------------------
Was thinking about this some more after looking at the patch. There is some use
in having this separation. If nothing else, it provides an idea of which of the
configs in TezRuntimeConfiguration is applicable to specific Inputs / Outputs.
Wondering if there's a good way to maintain this without ending up with
situations where a config is added but will not work.
One option that comes to mind is to have a test validate the number of entries
in TezRuntiemConfiguration. The test failure message explicitly tells users
what to do in terms of making sure the new config is added to the Inputs /
Ouputs where it needs to be used. (This would assume that existing configs are
not being enabled for Inputs/Outputs). Any other suggestions?
> 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)
