[
https://issues.apache.org/jira/browse/OOZIE-906?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ashish Vaidya updated OOZIE-906:
--------------------------------
Attachment: graphFRShape.png
This is the graph I obtained using JUNG 2.0.1 library. It's real workflow
that's being used in one of our products. To prevent giving away details of the
product I've used action type to label the vertices of the graph. In the final
code action names will be used.
The graph will paint the vertices according to the status of the actions at the
time of rendering. Thus, an OK will be green, PREP or RUNNING will be yellow,
KILLED, ERROR or FAILED will be RED. The nodes for which no info is yet
available will be painted light grey. For now I've just painted the graph to
highlight the various actions, but going forward it'll be per above coloring
scheme.
I've used FRLayout algorithm to chart the graph. This algo seems to do a good
job save for the fact that the orientation of the graph is not deterministic.
Thus, the same graph when rendered again shows up differently. If anyone out
there has any ideas to get this right please ping me on this JIRA.
Other comments and suggestions are most welcome.
Thanks,
Ashish
> 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
> Labels: graphical, job_graph, runtime_job_graph
> Attachments: 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
