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 Wed, 03 Dec 2014 15:43:12 GMT


Christian Tzolov updated CRUNCH-438:
    Attachment: CRUNCH-438.4.patch

I've updated the patch to the latest master. 

Also I have:
- Moved all dotfile writers into package
- To enable the extra dot files one has to set the PIPELINE_DOTFILE_OUTPUT_DIR (location where
they will be stored and a new DETAIL_DOTFILE_PLAN configuration set to 'true'). E.g.: 
    conf.set(PlanningParameters.DETAIL_DOTFILE_PLAN, "true") ;
    conf.get(PlanningParameters.PIPELINE_DOTFILE_OUTPUT_DIR, <folder>);
- Replaced the exec .getPlanDotFile() by getNamedDotFiles(): Map<String, String> to
support multiple named dot files. The main dotfile names is jobplane. 
- The MRPipeline#runAsync() runs through all mrExecutor.getNamedDotFiles() and writes them
in the output PIPELINE_DOTFILE_OUTPUT_DIR folder using the existing name notations
- Other smamll changes

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