Mailing-List: contact dev-help@crunch.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@crunch.apache.org
Date: Tue, 8 Jul 2014 13:59:05 +0000 (UTC)
From: "Christian Tzolov (JIRA)" <jira@apache.org>
To: crunch-dev@incubator.apache.org
Message-ID: <JIRA.12725618.1404643575811.911.1404827945372@arcas>
In-Reply-To: <JIRA.12725618.1404643575811@arcas>
References: <JIRA.12725618.1404643575811@arcas>
Subject: [jira] [Updated] (CRUNCH-438) Visualizations of some important
 internal/intermediate pipeline planning states
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


     [ 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.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 properties:
* PCOLLECTION_LINEAGE_DOTFILE 
* BASE_GRAPH_PLAN_DOTFILE
* SPLIT_GRAPH_PLAN_DOTFILE
* RTNODES_PLAN_DOTFILE

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: org.apache.crunch.impl.mr.plan.tracke


> 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.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
(v6.2#6252)