[jira] [Commented] (PIG-2586) A better plan/data flow visualizer

["Russell Jurney (Commented) (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/PIG-2586?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13229503#comment-13229503 ] 

Russell Jurney commented on PIG-2586:
-------------------------------------

I would like to mentor this.  The way to go here is with a web interface to this data.  

For instance, using these libraries:

https://github.com/glejeune/Ruby-Graphviz
http://www.sinatrarb.com/
http://neyric.github.com/wireit/

there would be enough time for a GSoC participant to really make serious progress at this.
                
> A better plan/data flow visualizer
> ----------------------------------
>
>                 Key: PIG-2586
>                 URL: https://issues.apache.org/jira/browse/PIG-2586
>             Project: Pig
>          Issue Type: Improvement
>          Components: impl
>            Reporter: Daniel Dai
>              Labels: gsoc2012
>
> Pig supports a dot graph style plan to visualize the logical/physical/mapreduce plan (explain with -dot option, see http://ofps.oreilly.com/titles/9781449302641/developing_and_testing.html). However, dot graph takes extra step to generate the plan graph and the quality of the output is not good. It's better we can implement a better visualizer for Pig. It should:
> 1. show operator type and alias
> 2. turn on/off output schema
> 3. dive into foreach inner plan on demand
> 4. provide a way to show operator source code, eg, tooltip of an operator (plan don't currently have this information, but you can assume this is in place)
> 5. besides visualize logical/physical/mapreduce plan, visualize the script itself is also useful
> 6. may rely on some java graphic library such as Swing
> This is a candidate project for Google summer of code 2012. More information about the program can be found at https://cwiki.apache.org/confluence/display/PIG/GSoc2012

--
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