[jira] [Updated] (CRUNCH-438) Visualizations of some important internal/intermediate pipeline planning states

["Christian Tzolov (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/CRUNCH-438?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Christian Tzolov updated CRUNCH-438:
------------------------------------

    Attachment: CRUNCH-438.patch

Attached is an initial prototype which implements 3 dotfile writers:
1. DotfileWriterPCollectionLineage - visualizes pcollection leneage
2. DotfileWriterGraph - visualizes the planning graph and components split
3. DotfileWriterRTNodes - visualize the RT nodes, inputs and outputs as de-seriazlied from the Configuration properties. 
All writers inherit from a common CommonDotfileWriter

The interception is hardcoded into MSCRPlanner#plan() method using the LOG.info to print the result dotfile visualizations.

- Addition getters were added to the RTNodes to access the internal attributes
- CrunchOutputs OutputConfig and CrunchOutputs.getNamedOutputs() methods have been extended to make them accessible in the dotfile writer. 

> Visualizations of some important internal/intermediate pipeline planning states
> -------------------------------------------------------------------------------
>
>                 Key: CRUNCH-438
>                 URL: https://issues.apache.org/jira/browse/CRUNCH-438
>             Project: Crunch
>          Issue Type: Improvement
>          Components: Core
>    Affects Versions: 0.10.0, 0.8.3
>            Reporter: Christian Tzolov
>            Assignee: Christian Tzolov
>         Attachments: CRUNCH-438.patch
>
>
> To improve the understability of the pipeline planning stages it would help to visualize some intermediate planning states like:
> - PCollection lineage. (visualizing the output-pcollection-targets structure) 
> - MSCRPlanner's planning Graphs before and after the split up of dependent GBK nodes
> - RTNode hierarchy along with the Input and Output configurations as persistent in the Configuration before the execution of the pipeline. 
> Most of the information can be intercepted in the MSCRPlanner#plan()  method.



--
This message was sent by Atlassian JIRA
(v6.2#6252)