You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@tez.apache.org by "Jonathan Eagles (JIRA)" <ji...@apache.org> on 2015/06/02 22:03:49 UTC
[jira] [Commented] (TEZ-2523) Tez UI: derive applicationId from
dag/vertex id instead of relying on json data
[ https://issues.apache.org/jira/browse/TEZ-2523?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14569658#comment-14569658 ]
Jonathan Eagles commented on TEZ-2523:
--------------------------------------
Seems to be fine.
> Tez UI: derive applicationId from dag/vertex id instead of relying on json data
> -------------------------------------------------------------------------------
>
> Key: TEZ-2523
> URL: https://issues.apache.org/jira/browse/TEZ-2523
> Project: Apache Tez
> Issue Type: Bug
> Components: UI
> Reporter: Prakash Ramachandran
> Assignee: Prakash Ramachandran
> Attachments: TEZ-2523.1.patch
>
>
> currently the applicationId for the models dag/vertex is picked up from primary filter data for the dag/vertex json. deriving this from the dagid/vertexid on the models has the below benefits.
> * ensures applicationId is not null (in some corner cases this causes exception in store.find)
> * makes the ui backward compatible (0.5).
> * allows to remove the appid from primary filter (TEZ-2485)
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)