[
https://issues.apache.org/jira/browse/TEZ-1233?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14314905#comment-14314905
]
Bikas Saha commented on TEZ-1233:
---------------------------------
I don't have further comments about the code in the patch. Perhaps it would
help if some of the examples could use the API to do something useful.
Overall, though, its unclear to me why we are making the programmatic change
and not the configuration based change. Eg. If I have to take a job thats
having issues and want to rerun it once with a different config for a given
vertex then can I do that after this change?
Thinking about the comments here and in TEZ-2003, I would expect that a clear
ExecutionContext like API would be created that would allow different execution
contexts to be specified per vertex in an unambiguous and clearly defined
manner. Instead it seems like the functionality depends on correctly setting a
bunch of independent configuration properties via a configuration based API.
Apart from being error prone, in general we have tried to stay clear of
configuration based API's in Tez. So the change concerns me.
> 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,
> TEZ-1233-4.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)
