Mailing-List: contact dev-help@crunch.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@crunch.apache.org
Date: Tue, 14 Jan 2014 23:21:20 +0000 (UTC)
From: "Josh Wills (JIRA)" <jira@apache.org>
To: crunch-dev@incubator.apache.org
Message-ID: <JIRA.12687690.1389115375374.1767.1389741680247@arcas>
In-Reply-To: <JIRA.12687690.1389115375374@arcas>
References: <JIRA.12687690.1389115375374@arcas>
Subject: [jira] [Commented] (CRUNCH-320) Materialize several PObject &
 PCollection objects in parallel (deferred materialization)
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Josh Wills commented on CRUNCH-320:
-----------------------------------

No worries Jason; I'm confident it will work correctly.

> Materialize several PObject & PCollection objects in parallel (deferred materialization)
> ----------------------------------------------------------------------------------------
>
>                 Key: CRUNCH-320
>                 URL: https://issues.apache.org/jira/browse/CRUNCH-320
>             Project: Crunch
>          Issue Type: Improvement
>          Components: Core
>            Reporter: Jason Gauci
>            Assignee: Josh Wills
>             Fix For: 0.10.0, 0.8.3
>
>         Attachments: CRUNCH-320.patch
>
>
> Currently, Crunch blocks and materializes PCollections (through foo.materialize()) and PObjects (through foo.getValue()) on demand, but it would be a significant performance improvement if we could mark several of these objects as to be materialized, and then materialize all of them in parallel as part of a pipeline.run() call.


--
This message was sent by Atlassian JIRA
(v6.1.5#6160)