crunch-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Christian Tzolov (JIRA)" <>
Subject [jira] [Updated] (CRUNCH-438) Visualizations of some important internal/intermediate pipeline planning states
Date Tue, 08 Jul 2014 13:59:05 GMT


Christian Tzolov updated CRUNCH-438:

    Attachment: CRUNCH-438.3.patch

Gabriel i think your point makes sense. So i've attached a new patch (v3) that removes the
functionality that writes dotfiles into the PIPELINE_DOTFILE_OUTPUT_DIR folder. Also i've
fixed (hopefully) the spelling names. The debug diagrams will be stored i the following configuration

Would it make sense to enable the 'debug' dotfiles generation only if the pipeliene.enbableDebug()
is set? 
Also shall we move all DotfileWriter... clases into a dedicated package? For example:

> Visualizations of some important internal/intermediate pipeline planning states
> -------------------------------------------------------------------------------
>                 Key: CRUNCH-438
>                 URL:
>             Project: Crunch
>          Issue Type: Improvement
>          Components: Core
>    Affects Versions: 0.10.0, 0.8.3
>            Reporter: Christian Tzolov
>            Assignee: Christian Tzolov
>         Attachments: CRUNCH-438.2.patch, CRUNCH-438.3.patch, 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

View raw message