[ https://issues.apache.org/jira/browse/TEZ-1233?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14311842#comment-14311842 ]
Jeff Zhang commented on TEZ-1233: --------------------------------- Upload initial patch by using Annotation. * add annotation to all the property in TezConfiguration * add new API for DAG/Vertex, and restrict the usage of different level of property by using annotation ** DAG.setDAGConf(key,value) ** Vertex.setVertexConf(key,value) * In the AM side, each DAG has its own copy of Configuration, and each Vertex also has its own copy of Configuration. * Leave the property which is used for setting vertex level configuration by using vertex name to retain the compatibility. * Haven't verify whether each property is correctly through the correct configuration. This patch is only to making it possible for set different level of configuration * The property in tez-site.xml are all AM level configuration * All the property used in tez-runtime are all AM level, can not been set at DAG/Vertex level because of container reuse. Except for the configuration of Input/Output which has already been done in TezRuntimeConfiguration. > 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 > > > 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)