[
https://issues.apache.org/jira/browse/TEZ-1700?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14189239#comment-14189239
]
Bikas Saha commented on TEZ-1700:
---------------------------------
Binary compatibility should be fine. Would be hard to do since 0.5.1 and 0.5.2
are already incompatible.
bq. "other.affinitizedTask != null"
Was just following the existing code flow. Will check this.
bq. affinityAttempt's container id?
Good catch. Will check why the existing test for affinity did not catch this.
> Replace containerId from TaskLocationHint with [TaskIndex+Vertex] based
> affinity
> --------------------------------------------------------------------------------
>
> Key: TEZ-1700
> URL: https://issues.apache.org/jira/browse/TEZ-1700
> Project: Apache Tez
> Issue Type: Bug
> Reporter: Bikas Saha
> Assignee: Bikas Saha
> Attachments: TEZ-1700.1.patch
>
>
> Today 1-1 dependencies are affinitized by creating a task location hint with
> the producer task container id. It can be created by affinitizing to the
> producer task-index+vertexname combination instead and internally Tez can map
> it to the container. This also allows this dependency to be specified before
> the container is assigned. This allows the dependency to be generic.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
