[
https://issues.apache.org/jira/browse/CRUNCH-176?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
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 Dave!
> CrunchTool limits access to some pipeline functionality
> -------------------------------------------------------
>
> Key: CRUNCH-176
> URL: https://issues.apache.org/jira/browse/CRUNCH-176
> 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: http://www.atlassian.com/software/jira
