You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@crunch.apache.org by "Josh Wills (JIRA)" <ji...@apache.org> on 2014/08/05 06:46:12 UTC
[jira] [Updated] (CRUNCH-405) Explore adding support for idempotent
MRPipeline.plan()
[ https://issues.apache.org/jira/browse/CRUNCH-405?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Josh Wills updated CRUNCH-405:
------------------------------
Attachment: CRUNCH-405.patch
[~mkwhitacre] took a crack at this in the attached patch. Want to take a look?
> Explore adding support for idempotent MRPipeline.plan()
> -------------------------------------------------------
>
> Key: CRUNCH-405
> URL: https://issues.apache.org/jira/browse/CRUNCH-405
> Project: Crunch
> Issue Type: Improvement
> Components: Core
> Reporter: Micah Whitacre
> Assignee: Micah Whitacre
> Attachments: CRUNCH-405.patch, CRUNCH-405_v1.patch
>
>
> Talking through a use case with a consumer, they were interested in having the ability to run the MRPipeline.plan() method one to many times prior to ever calling the Pipeline.run/done methods. The reason for this was they were looking at pulling information off the MRExecutor to tweak settings inside of their DoFns.
> Currently the MRPipeline implementation however does not have an idempotent plan() method as it alters the state of internal values therefore affecting the full run once done() is called.
> It would be nice if we added an idempotent plan() method that could be gather this information or perhaps a reset option.
--
This message was sent by Atlassian JIRA
(v6.2#6252)