Mailing-List: contact dev-help@crunch.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@crunch.apache.org
Date: Wed, 6 Aug 2014 02:40:12 +0000 (UTC)
From: "Micah Whitacre (JIRA)" <jira@apache.org>
To: crunch-dev@incubator.apache.org
Message-ID: <JIRA.12716906.1401224625322.22484.1407292812980@arcas>
In-Reply-To: <JIRA.12716906.1401224625322@arcas>
References: <JIRA.12716906.1401224625322@arcas>
Subject: [jira] [Commented] (CRUNCH-405) Explore adding support for
 idempotent MRPipeline.plan()
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


    [ https://issues.apache.org/jira/browse/CRUNCH-405?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14087158#comment-14087158 ] 

Micah Whitacre commented on CRUNCH-405:
---------------------------------------

Confirmed it is a timing issue, adding volatile keyword fixed test.  Still not sure we shouldn't add check to start/block to truly have correct behavior vs one that works.

> 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)