Return-Path: 
 <dev-return-4345-apmail-crunch-dev-archive=crunch.apache.org@crunch.apache.org>
X-Original-To: apmail-crunch-dev-archive@www.apache.org
Delivered-To: apmail-crunch-dev-archive@www.apache.org
Received: from mail.apache.org (hermes.apache.org [140.211.11.3])
	by minotaur.apache.org (Postfix) with SMTP id CE0DA11A79
	for <apmail-crunch-dev-archive@www.apache.org>;
 Fri, 16 May 2014 22:12:27 +0000 (UTC)
Received: (qmail 40676 invoked by uid 500); 16 May 2014 19:50:02 -0000
Delivered-To: apmail-crunch-dev-archive@crunch.apache.org
Received: (qmail 29686 invoked by uid 500); 16 May 2014 19:49:51 -0000
Mailing-List: contact dev-help@crunch.apache.org; run by ezmlm
Precedence: bulk
List-Help: <mailto:dev-help@crunch.apache.org>
List-Unsubscribe: <mailto:dev-unsubscribe@crunch.apache.org>
List-Post: <mailto:dev@crunch.apache.org>
List-Id: <dev.crunch.apache.org>
Reply-To: dev@crunch.apache.org
Delivered-To: mailing list dev@crunch.apache.org
Received: (qmail 22211 invoked by uid 99); 16 May 2014 19:41:49 -0000
Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136)
    by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 16 May 2014 19:41:49 +0000
X-ASF-Spam-Status: No, hits=1.7 required=5.0
	tests=FREEMAIL_ENVFROM_END_DIGIT,HTML_MESSAGE,RCVD_IN_DNSWL_LOW,SPF_PASS
X-Spam-Check-By: apache.org
Received-SPF: pass (athena.apache.org: domain of anujojha5@gmail.com
 designates 209.85.128.173 as permitted sender)
Received: from [209.85.128.173] (HELO mail-ve0-f173.google.com)
 (209.85.128.173)
    by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 16 May 2014 19:41:44 +0000
Received: by mail-ve0-f173.google.com with SMTP id pa12so3631864veb.4
        for <dev@crunch.apache.org>; Fri, 16 May 2014 12:41:23 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
        d=gmail.com; s=20120113;
        h=mime-version:from:date:message-id:subject:to:content-type;
        bh=SS5ktGWMePpGlGGMGBUxpP+MoWh6Jzo120Q6p4IB4QM=;
        b=VeLUvNkMtdo0Xn78V8iiBTAfmhlfn9MmvNCBsbJlAvKRShGZpAAtTJ1OQee0/zJnhc
         46Yq1hL9TiiQBSeZh9q3bLfgPkX0U7M81IGSlj8tJK5n/qSMSFtC+YUd89QOukXjQ2We
         nUYxqEemgKqf59beIKHRWgPygymsXIntTABKawE9JNvlYnA4lTwFgOh/1vTCn38AE2+N
         qX8COe0YxrYgXIj+4RFFWe9t7ZcHI0WZZQco1O7F0owPLUxs4vReKHEM6YRcJJ/Tz0EH
         gQe9qqI6XbOptNQ/ouSej1QJLhr4kqOxhEU99pRr+qFKTx32AcE0HvVkaDFIuozOrPTb
         TfjA==
X-Received: by 10.52.141.74 with SMTP id rm10mr13112329vdb.6.1400269283779;
 Fri, 16 May 2014 12:41:23 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.220.158.197 with HTTP; Fri, 16 May 2014 12:41:03 -0700 (PDT)
From: anuj ojha <anujojha5@gmail.com>
Date: Fri, 16 May 2014 14:41:03 -0500
Message-ID: 
 <CANFazTUAffvTctK5=WvW4KyBLSqLCNcke7ZMWwgASu+EtkDmyQ@mail.gmail.com>
Subject: Materialize running the pipeline and not giving stage result.
To: dev@crunch.apache.org
Content-Type: multipart/alternative; boundary=bcaec52c5e7b3fea2b04f9899980
X-Virus-Checked: Checked by ClamAV on apache.org

--bcaec52c5e7b3fea2b04f9899980
Content-Type: text/plain; charset=UTF-8

Hello All,
        I am doing the following in my pipeline:
{
some processing.
........
pcollections.materialize();

final PipelineResult pipelineResult = pipeline.run();


final List<StageResult> stageResults = pipelineResult.getStageResults();


}


I am trying to access stageresult and I am getting it as null. I can't
avoid calling materialize as I use the data which I get from materializing
pcollection in further processing. Is there another way to achieve what I
am doing above?

--bcaec52c5e7b3fea2b04f9899980--