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/01/07 18:27:52 UTC
[jira] [Commented] (CRUNCH-320) Materialize several PObject &
PCollection objects in parallel (deferred materialization)
[ https://issues.apache.org/jira/browse/CRUNCH-320?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13864418#comment-13864418 ]
Josh Wills commented on CRUNCH-320:
-----------------------------------
Is that not already the case? You can get a reference to the materialized collection (Iterable<T>) or the PObject, but we don't actually create it until you call iterator() on the Iterable<T> or getValue() on the PObject. You should be able to line up a bunch of materialized collections/PObjects, call run(), and then retrieve the materialized data immediately by calling iterator()/getValue() as appropriate.
> 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
>
> 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)