[
https://issues.apache.org/jira/browse/TEZ-1018?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13976323#comment-13976323
]
Bikas Saha edited comment on TEZ-1018 at 4/22/14 2:47 AM:
----------------------------------------------------------
bq. If not, final could still be retained and just hosts/racks to null.
We could. But then its not really matching any app semantics. We are just
making Java happy even though the semantics dont need rack/host to be set at
all times. Right? The final ensures that the fields must be set during object
creation. But we just relaxed that constraint because the object now has
another field that can replace those.
was (Author: bikassaha):
bq. If not, final could still be retained and just hosts/racks to null.
We could. But then its not really matching any app semantics. We are just
making Java happy even though the semantics dont need rack/host to be set at
all times. Right?
> VertexManagerPluginContext should enable assigning locality to scheduled tasks
> ------------------------------------------------------------------------------
>
> Key: TEZ-1018
> URL: https://issues.apache.org/jira/browse/TEZ-1018
> Project: Apache Tez
> Issue Type: Improvement
> Reporter: Bikas Saha
> Assignee: Bikas Saha
> Attachments: TEZ-1018.1.patch, TEZ-1018.2.patch, TEZ-1018.3.patch
>
>
> This may be used by VertexManager to decide the location of their tasks
> depending on the location of source tasks.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
