[
https://issues.apache.org/jira/browse/OOZIE-906?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13429571#comment-13429571
]
Ashish Vaidya commented on OOZIE-906:
-------------------------------------
I take back my previous comment. I figured out a way to order the nodes per
their order of occurance in the worflow XML. I'm attaching the code patch of
the work so far.
- The REST API to access the graph is v1/job/{jobid}?show=graph. This is not,
an perhaps won't be, available in v0 of the REST API.
- The graph is rendered from top to bottom, and delivered to the client in PNG
format.
- The nodes that haven't yet started execution are painted gray. The nodes that
are prepping or running are painted yellow. The nodes that have completed their
execution successfully are painted green, and the ones that have failed/errored
out are painted red.
- The error target (typically a kill node) is shown with dashed arrow. If we
reach this kill node, it's painted red.
- I found that fork node doesn't carry any execution info. Thus, it remains
painted gray even if it has been executed.
> 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
