[
https://issues.apache.org/jira/browse/TEZ-963?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13941973#comment-13941973
]
Hitesh Shah commented on TEZ-963:
---------------------------------
[~airbots] Not upset at all :). And yes, agreed that we need documentation on
the configuration parameters.
To take a step back, what I am against is having TezConfiguration have
something like "addDefaultResource(tez-default.xml)" in it ( which is what
HDFS/MR/YARN, etc. do for their own default xml files ).
I would actually like to have a tez-default.xml however it should not be
hand-edited and should be generated at compile time using the fields in
TezConfiguration ( we can figure out a way to do this via reflection or
something ). This generated default file should never be loaded into a process
at run-time by any part of the framework. It should just be a
documentation-related helper file but not required for any run-time logic. Does
that help clarify what my concerns are?
> TezConfiguration should have tez-default.xml like other Hadoop projects
> -----------------------------------------------------------------------
>
> Key: TEZ-963
> URL: https://issues.apache.org/jira/browse/TEZ-963
> Project: Apache Tez
> Issue Type: Bug
> Reporter: Chen He
>
> Like other Hadoop projects: MapReduce, Yarn, HDFS, etc. They all have two
> configuration files. One is *-default.xml which contains default values, the
> other is *-site.xml which allows user to customize configurations.
--
This message was sent by Atlassian JIRA
(v6.2#6252)