You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@tez.apache.org by "Rajesh Balamohan (JIRA)" <ji...@apache.org> on 2016/02/05 01:31:39 UTC

[jira] [Assigned] (TEZ-3093) CriticalPathAnalyzer should be accessible via zeppelin

     [ https://issues.apache.org/jira/browse/TEZ-3093?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Rajesh Balamohan reassigned TEZ-3093:
-------------------------------------

    Assignee: Rajesh Balamohan

> CriticalPathAnalyzer should be accessible via zeppelin
> ------------------------------------------------------
>
>                 Key: TEZ-3093
>                 URL: https://issues.apache.org/jira/browse/TEZ-3093
>             Project: Apache Tez
>          Issue Type: Improvement
>            Reporter: Rajesh Balamohan
>            Assignee: Rajesh Balamohan
>         Attachments: TEZ-3093.1.patch
>
>
> CriticalPathAnalyzer is mainly used as a standalone tool (via yarn jar command). However, it should be possible to integrate this with tools like zeppelin where in this can be accessed in spark context. For e.g
> {code}
> var config = new Configuration()
> config.set("tez.critical-path-analyzer.svg-dir", "/tmp/html/analyzer/criticalPath/")
> config.set("tez.critical-path-analyzer.draw-svg", "true")
> var criticalPathAnalyzer = new CriticalPathAnalyzer(config)
> criticalPathAnalyzer.analyze(dagInfo)
> var cpResult = criticalPathAnalyzer.getResult
> {code}



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