[
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.8.patch
Another round-trip to resolve:
- A bit of the plan-execution logic was incorrectly moved inside the
DotfileUtilities.java. This logic has been returned to the MSCRPlanner#plan().
The DotfileUtilites provisions only the Dotfile generation. Any exception
thrown there should not affect the main planning logic.
- Use the git fomrat-patch to generate the patch (earlier patches were
generated with git diff)
- remove some trailing whitespaces
> 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.7.patch, CRUNCH-438.8.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)
