[
https://issues.apache.org/jira/browse/OOZIE-576?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13124648#comment-13124648
]
Jacob Perkins commented on OOZIE-576:
-------------------------------------
I would really rather not write a parser to create the workflow
description/graph structure when oozie must be doing this work internally.
Could someone please point me to the classes responsible for this work?
Also, any thoughts on general approach/where it fits?
> Workflow Visualization
> ----------------------
>
> Key: OOZIE-576
> URL: https://issues.apache.org/jira/browse/OOZIE-576
> Project: Oozie
> Issue Type: New Feature
> Reporter: Jacob Perkins
> Priority: Minor
>
> An oozie workflow can naturally be described with a directed graph. It should
> be possible to create a visual representation of an oozie workflow as such by
> parsing the workflow definition, resolving any references to sub-workflows,
> and creating a nested set of classes that describe the full workflow. This
> description could then be serialized as json and visualized with a javascript
> library like d3.js (or something along those lines) for display and possibly
> even interaction.
> Important details here include displaying hierarchy (top-level workflow vs.
> sub-workflow) in a clear way and distinguishing between other types of
> actions (java, pig, fs, etc..).
--
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
