[
https://issues.apache.org/jira/browse/TEZ-1065?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14082615#comment-14082615
]
Bikas Saha commented on TEZ-1065:
---------------------------------
Lets do it here and change the title. This may be more work. So I removed this
from 0.5 blocker list. We could do the topological ordering in the TezClient
itself before job submission and use the changes in the current patch to
maintain that order in the AM.
> DAGStatus.getVertexStatus and other vertex related API's should maintain
> vertex order
> -------------------------------------------------------------------------------------
>
> Key: TEZ-1065
> URL: https://issues.apache.org/jira/browse/TEZ-1065
> Project: Apache Tez
> Issue Type: Bug
> Affects Versions: 0.5.0
> Reporter: Bikas Saha
> Assignee: Jeff Zhang
> Labels: newbie
> Attachments: TEZ-1065.1.patch, Tez-1065-2.patch, Tez-1065.patch
>
>
> They should maintain the incoming vertex order. In VertexProgress e.g. lets
> use LinkedHashMap instead of HashMap.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
