[
https://issues.apache.org/jira/browse/TEZ-1233?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14313753#comment-14313753
]
Jeff Zhang commented on TEZ-1233:
---------------------------------
bq. While its probably fine to allow programmatic access, it seems incomplete
without allowing configuration to be changed via configuration files.
configuration files can still been used. This jira add new api to allow
programmatic set the dag/vertex level configuration to override the
configuration file and add new configuration per dag/vertex. Regarding the
relationship with TEZ-2003, I think the per vertex configuration is
specifically for external executor service (LLAP) that is not general for Tez.
> 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
> Attachments: TEZ-1233-1.patch, TEZ-1233-2.patch, TEZ-1233-3.patch
>
>
> 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)
