[ 
https://issues.apache.org/jira/browse/TEZ-2076?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14337015#comment-14337015
 ] 

Gopal V commented on TEZ-2076:
------------------------------

bq. It would catch any regressions that may be caused by an update to the event 
writing code that does not make corresponding changes to this in-memory model.

I agree, a regression test would be a great thing to do once this starts 
producing useful output, particularly because that serves as a safety check for 
the Tez-UI, since they would share data models. 

But until we manually verify the semantics there's no scope for automated 
testing.

The current problem of the highest priority is the currently present loss of 
information that is happening inside the DAGAppMaster.

Analysis using this parser highlights those issues that we need to fix as 
follow-up JIRAs on the AM before we can write regression suites. 

> Tez framework to extract/analyze data stored in ATS for specific dag
> --------------------------------------------------------------------
>
>                 Key: TEZ-2076
>                 URL: https://issues.apache.org/jira/browse/TEZ-2076
>             Project: Apache Tez
>          Issue Type: Improvement
>            Reporter: Rajesh Balamohan
>            Assignee: Rajesh Balamohan
>         Attachments: TEZ-2076.1.patch, TEZ-2076.2.patch, TEZ-2076.3.patch, 
> TEZ-2076.WIP.2.patch, TEZ-2076.WIP.3.patch, TEZ-2076.WIP.patch
>
>
> - Users should be able to download ATS data pertaining to a DAG from Tez-UI 
> (more like a zip file containing DAG/Vertex/Task/TaskAttempt info).
> - This can be plugged to an analyzer which parses the data, adds semantics 
> and provides an in-memory representation for further analysis.
> - This will enable to write different analyzer rules, which can be run on top 
> of this in-memory representation to come up with analysis on the DAG.
> - Results of this analyzer rules can be rendered on to UI (standalone webapp) 
> later point in time.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Reply via email to