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/05/27 22:31:03 UTC
[jira] [Commented] (CRUNCH-400) Materialized jobs should have stage
in PipelineResult
[ https://issues.apache.org/jira/browse/CRUNCH-400?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14010226#comment-14010226 ]
Josh Wills commented on CRUNCH-400:
-----------------------------------
So I'm confused how this happens; the StageResults relate to the jobs that were run, not necessarily the outputs (since multiple outputs can correspond to a single job.) It's also the case that if you materialize an existing PCollection, then no job needs to be run to create it, hence no StageResults.
> Materialized jobs should have stage in PipelineResult
> -----------------------------------------------------
>
> Key: CRUNCH-400
> URL: https://issues.apache.org/jira/browse/CRUNCH-400
> Project: Crunch
> Issue Type: Improvement
> Components: Core
> Affects Versions: 0.9.0, 0.8.2
> Reporter: Micah Whitacre
>
> Brought up as part of the proposed fix for CRUNCH-272 and on the mailing list[1], a set of jobs kicked off due to a materialize() call will not be tracked as part of the Pipeline's stage results returned by the PipelineResult.
> [1] - http://mail-archives.apache.org/mod_mbox/crunch-dev/201405.mbox/%3CCANFazTUAffvTctK5%3DWvW4KyBLSqLCNcke7ZMWwgASu%2BEtkDmyQ%40mail.gmail.com%3E
--
This message was sent by Atlassian JIRA
(v6.2#6252)