crunch-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Josh Wills (JIRA)" <>
Subject [jira] [Resolved] (CRUNCH-176) CrunchTool limits access to some pipeline functionality
Date Tue, 05 Mar 2013 16:45:11 GMT


Josh Wills resolved CRUNCH-176.

       Resolution: Fixed
    Fix Version/s: 0.6.0

Agreed-- nice fixes. I made a couple of tweaks: first, I added runAsync() to the list of built-in
methods, and second, I marked the Pipeline object used by CrunchTool as transient so that
serialization will work properly (Pipeline instances are not usually serializable.)  Thanks
> CrunchTool limits access to some pipeline functionality
> -------------------------------------------------------
>                 Key: CRUNCH-176
>                 URL:
>             Project: Crunch
>          Issue Type: Improvement
>          Components: Core
>            Reporter: Dave Beech
>            Assignee: Josh Wills
>            Priority: Minor
>             Fix For: 0.6.0
>         Attachments: CRUNCH-176.patch
> CrunchTool is a really handy way to start a Crunch job, but it unnecessarily limits some
of the features of Pipeline. 
> Some suggested improvements:
> - run() and done() methods could return the PipelineResult returned by the pipeline
> - CrunchTool could be Serializable so you don't have to remember to add this to yourself
after writing anonymous DoFns
> - add materialize method?
> - could even provide access to the underlying pipeline object via a protected getter?

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see:

View raw message