[
https://issues.apache.org/jira/browse/TEZ-1080?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14036452#comment-14036452
]
Siddharth Seth commented on TEZ-1080:
-------------------------------------
bq. But this is going to add a lot of checks to pig and hive code. And also if
Tez introduced a new setting we will have to make code changes and set that and
will have to roll out a new release instead of the new setting just taking
effect by passing it via tez-site.xml, pig-site.xml or command line like now.
This is exposing the commonly used settings via APIs. Settings which are
typically not used by users are specified via a key-value map. tez-site.xml
continues to be respected in any case, so that would cover new settings (the
default value) when such new settings are added. The naming I think needs to be
fairly consistent so that it is easy to detect which ones need to be used and
which do not.
Tez will likely add a helper to extract out necessary settings.
> Configuration for non MR based Inputs/Outputs
> ---------------------------------------------
>
> Key: TEZ-1080
> URL: https://issues.apache.org/jira/browse/TEZ-1080
> Project: Apache Tez
> Issue Type: Sub-task
> Reporter: Siddharth Seth
> Assignee: Siddharth Seth
> Attachments: TEZ-1080.wip.1.txt, TEZ-1080.wip.2.txt
>
>
> De-link configuration from MRHelpers (except for the YARNRunner case), and
> allow for these to be configured easily - exposing necessary setters /
> getters without having to rely on config keys.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
