[
https://issues.apache.org/jira/browse/TEZ-1233?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14308662#comment-14308662
]
Jeff Zhang commented on TEZ-1233:
---------------------------------
bq. For the runtime layer - we setup allowed config parameters in maps (see
TezRuntimeConfiguration and any of the Inputs / Outputs). Annotations couldn't
be used there since the properties are used by modules which
TezRuntimeConfiguration is not aware of. Otherwise, annotations seems like a
nice way to achieve this.
As my understanding, TezRuntimeConfiguration is used for the configuration in
LogicalIOProcessorRuntimeTask (mainly for I/P/O). Looks like we have already
support the edge level configuration through XXEdgeConf.setFromConfiguration.
The configuration is wrapped into the payload of Input/Output. And each
Input/Output can have its own copy of Configuration. So I think it may be OK to
not take into account TezRuntimeConfiguraion.
> 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)
