[
https://issues.apache.org/jira/browse/TEZ-1233?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14304884#comment-14304884
]
Jeff Zhang commented on TEZ-1233:
---------------------------------
Start from dag level configuration make sense for me. I plan to build 3 levels
of configuration: session/dag/vertex. Each one will overlap configuration above
it.
With container re-use - for the property used in runtime (TezChild), I don't
think we need to support it for now. May leave it for future.
For what kind of configuration take effect in what level, I think there are 2
options:
* Add doc in TezConfiguration to tell what level this property would take
effect.
* Restrict the property usage in the API level. One way I think of is adding
annotation to each property, and verify it when user set the property in
DAG/Vertex.
> Allow configuration of framework parameters per vertex
> ------------------------------------------------------
>
> Key: TEZ-1233
> URL: https://issues.apache.org/jira/browse/TEZ-1233
> Project: Apache Tez
> Issue Type: Improvement
> Reporter: Siddharth Seth
> Assignee: Jeff Zhang
>
> Currently, configuration properties specific in AMConfiguration are used to
> configure tasks - e.g. memory configs, process tree, etc. These should be
> configurable at a Vertex level.
> Also, tasks end up reading these configs from the dist cache each time -
> would be simpler to send over the wire as part of the TaskSpec.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
