Mailing-List: contact dev-help@crunch.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@crunch.apache.org
Date: Sun, 6 Jul 2014 18:59:34 +0000 (UTC)
From: "Gabriel Reid (JIRA)" <jira@apache.org>
To: crunch-dev@incubator.apache.org
Message-ID: <JIRA.12725618.1404643575811.9382.1404673174242@arcas>
In-Reply-To: <JIRA.12725618.1404643575811@arcas>
References: <JIRA.12725618.1404643575811@arcas>
Subject: [jira] [Commented] (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:comment-tabpanel&focusedCommentId=14053187#comment-14053187 ] 

Gabriel Reid commented on CRUNCH-438:
-------------------------------------

Agree with Josh on the coolness of this, I'm super-excited about this one.

Do we want to write these files on every run as in CRUNCH-418? I'm thinking that they're more of a planner debugging tool (although maybe I'm seeing that wrong), so maybe it would be better to just stick them in the Configuration object as is done with the end-plan dot file. I've got the feeling that it might be a bit confusing for someone who just wants to see what their actual job plan looks like to get four different options.

Also, one tiny nit: the RTNode#getEmiter method name should be getEmitter, although as far as I can see it's not used anywhere so it can probably just be dropped.


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