[
https://issues.apache.org/jira/browse/TEZ-3093?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15133565#comment-15133565
]
Rajesh Balamohan commented on TEZ-3093:
---------------------------------------
committed addendum to master:
>>>
commit c7397f5de42bd83f2a479ca1b29ef007cc40cc25
>>>
>>>
branch-0.7:
commit 087c942800be39064571e81c6087a6cca1d217ca
commit 7b5e692f48833bccc747a75ac490d5a0b9574f5d
>>>
> 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
> Fix For: 0.7.1, 0.8.3
>
> Attachments: TEZ-3093.1.patch, TEZ-3093.2.patch,
> TEZ-3093.addendum.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)
