tez-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "TezQA (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (TEZ-3093) CriticalPathAnalyzer should be accessible via zeppelin
Date Tue, 02 Feb 2016 13:36:39 GMT

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

TezQA commented on TEZ-3093:

{color:red}-1 overall{color}.  Here are the results of testing the latest attachment
  against master revision 89bc6ab.

    {color:green}+1 @author{color}.  The patch does not contain any @author tags.

    {color:red}-1 tests included{color}.  The patch doesn't appear to include any new or modified
                        Please justify why no new tests are needed for this patch.
                        Also please list what manual steps were performed to verify this patch.

    {color:green}+1 javac{color}.  The applied patch does not increase the total number of
javac compiler warnings.

    {color:green}+1 javadoc{color}.  There were no new javadoc warning messages.

    {color:green}+1 findbugs{color}.  The patch does not introduce any new Findbugs (version
3.0.1) warnings.

    {color:green}+1 release audit{color}.  The applied patch does not increase the total number
of release audit warnings.

    {color:green}+1 core tests{color}.  The patch passed unit tests in .

Test results: https://builds.apache.org/job/PreCommit-TEZ-Build/1449//testReport/
Console output: https://builds.apache.org/job/PreCommit-TEZ-Build/1449//console

This message is automatically generated.

> 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

View raw message