[
https://issues.apache.org/jira/browse/OOZIE-906?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13429607#comment-13429607
]
Robert Kanter commented on OOZIE-906:
-------------------------------------
Good Job, that looks really great.
Two things:
1) Perhaps we should change some of the colors? The bright red is kinda hard
of the eyes and the dark grey on black for the end node makes it difficult to
read.
2) How "expensive" is it to generate the graph image? It looks like you
generate a new graph each time a request is made, so I'd be concerned that
someone spamming the refresh button could cause a problem on a large workflow.
Is there some way to save the graphs once they are generated and then just
update them when things change?
> Show runtime job DAG visually in Oozie console/dashboard
> --------------------------------------------------------
>
> Key: OOZIE-906
> URL: https://issues.apache.org/jira/browse/OOZIE-906
> Project: Oozie
> Issue Type: New Feature
> Reporter: Ashish Vaidya
> Assignee: Ashish Vaidya
> Labels: graphical, job_graph, runtime_job_graph
> Attachments: GraphGenerator.java, OOZIE-906.patch, Sample runtime
> DAG.png, graphFRShape.png
>
> Original Estimate: 504h
> Remaining Estimate: 504h
>
> The browser based Oozie console (the one currently written in ExtJS) shows
> the following tags when one clicks on a job to see its details:
> - Job Info
> - Job Definition
> - Job Configuration
> - Job Log
> It is desired to add a visual representation of the job DAG. An additional
> tag (likely called Job Graph) will be provided in the above console that
> will, when clicked, show the job workflow diagrammatically.
> The nodes in the graph/diagram will be color coded to represent their current
> state (Red for error/kill/failure, Green for OK and Yellow for the rest; or
> some combination thereof).
> The nodes will have names as provided in the job definition. The nodes may
> also be of different shapes (per action/control node) for better visibility.
> They may also carry some basic info like start time and duration.
> As regards implementation, it will be a server side with an HTTP API URL as
> invoker. The graphing may be done using GraphViz APIs, provided we find those
> to be Apache License compliant.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
