Mailing-List: contact issues-help@tez.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@tez.apache.org
Date: Thu, 4 Feb 2016 18:49:39 +0000 (UTC)
From: "Rajesh Balamohan (JIRA)" <jira@apache.org>
To: issues@tez.apache.org
Message-ID: <JIRA.12935947.1454415972000.301548.1454611779847@Atlassian.JIRA>
In-Reply-To: <JIRA.12935947.1454415972000@Atlassian.JIRA>
References: <JIRA.12935947.1454415972000@Atlassian.JIRA>
 <JIRA.12935947.1454415972548@arcas>
Subject: [jira] [Commented] (TEZ-3093) CriticalPathAnalyzer should be
 accessible via zeppelin
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Rajesh Balamohan commented on TEZ-3093:
---------------------------------------

Normally, output-dir is populated by parsing the command line arguments passed.  But OutputDir is not populated when zeppelin is used OOTB. 

> 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
>         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)