Mailing-List: contact dev-help@crunch.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@crunch.apache.org
Date: Fri, 5 Dec 2014 23:53:12 +0000 (UTC)
From: "Josh Wills (JIRA)" <jira@apache.org>
To: crunch-dev@incubator.apache.org
Message-ID: <JIRA.12725618.1404643575000.89578.1417823592956@Atlassian.JIRA>
In-Reply-To: <JIRA.12725618.1404643575000@Atlassian.JIRA>
References: <JIRA.12725618.1404643575000@Atlassian.JIRA>
 <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=14236322#comment-14236322 ] 

Josh Wills commented on CRUNCH-438:
-----------------------------------

+1 from me, just a couple of nits:

1) It looks like some of the new files ended up being tab-delimited instead of using spaces.
2) Couple of places where blocks and fields are commented out that should be deleted (e.g., planDotFile member var, a block in the doBuildDiagram method).

Thanks-- really excellent improvement to debugging!

> 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.4.patch, CRUNCH-438.5.patch, CRUNCH-438.6.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.3.4#6332)