[
https://issues.apache.org/jira/browse/OOZIE-906?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13429922#comment-13429922
]
Ashish Vaidya commented on OOZIE-906:
-------------------------------------
Thanks for the inputs, Robert. We can always decide on an eye-pleasing color
scheme. I just picked the colors that are available readily in Java Color class.
As for the expense of generating it, it depends on how complex the workflow is.
The very first picture that I posted to this JIRA is from a workflow XML that's
over 2500 lines, and certainly takes a handful of seconds to generate and is
quite a bit in size. While, some others are single node workflows which are
very easily generated.
I'm not aware of any webserver level response caching mechanism in Oozie. If
one exists then we can certainly do some timestamp comparison to avoid
regenerating the graph if nothing has changed.
One thing that I found strange is the REST API assumes the output will be JSON
for most parts. Writing PNG generation API using a class derived from
JsonRestServlet seems a bit unnatural... but I digress.
> 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
