Return-Path: Delivered-To: apmail-uima-user-archive@www.apache.org Received: (qmail 24249 invoked from network); 9 Jul 2010 11:09:30 -0000 Received: from unknown (HELO mail.apache.org) (140.211.11.3) by 140.211.11.9 with SMTP; 9 Jul 2010 11:09:30 -0000 Received: (qmail 70584 invoked by uid 500); 9 Jul 2010 11:09:29 -0000 Delivered-To: apmail-uima-user-archive@uima.apache.org Received: (qmail 70353 invoked by uid 500); 9 Jul 2010 11:09:27 -0000 Mailing-List: contact user-help@uima.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: user@uima.apache.org Delivered-To: mailing list user@uima.apache.org Received: (qmail 70345 invoked by uid 99); 9 Jul 2010 11:09:26 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 09 Jul 2010 11:09:26 +0000 X-ASF-Spam-Status: No, hits=0.0 required=10.0 tests=FREEMAIL_FROM,SPF_PASS,T_TO_NO_BRKTS_FREEMAIL X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of eaepstein@gmail.com designates 74.125.82.49 as permitted sender) Received: from [74.125.82.49] (HELO mail-ww0-f49.google.com) (74.125.82.49) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 09 Jul 2010 11:09:19 +0000 Received: by wwi14 with SMTP id 14so8296670wwi.30 for ; Fri, 09 Jul 2010 04:08:57 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:received:in-reply-to :references:date:message-id:subject:from:to:content-type; bh=PDHvIhuSTQL0w6L+Sr/O/t0sXlZsDYKUfBPqsyH91nw=; b=gfwCJQgEW2f9a2fFW/BVg9qb4CxZel7xSt8Jwr8BIUBax/azj4KXI/DLmhuQOjQPcj psncOUcNH2PRSpxdwMSsCiPwuFU6zBBqjK9wa7YNZXvf2AXiSHQCo7PMAlmavo3nEGpf vFSPiiZlC971QAms6rMe/p6uuLTMmS7IuB5R0= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; b=fjPnJiiJ8h7dnLO+V1HLdZ71Ne3F3WAPDcjQEIDfs+CztdTjNW5J50kqUeqpkT4MRM 3v7YhB1OkmFDl/Hzu738lPTJEoAyq3U/p8+8nakqqgwYhBzwdt+CUUSmsXjfd0fO1R1A XLuELAmJwjU0uwmV0t7hX3UWgDZWKmxuv5GAc= MIME-Version: 1.0 Received: by 10.216.167.13 with SMTP id h13mr3995850wel.80.1278673737791; Fri, 09 Jul 2010 04:08:57 -0700 (PDT) Received: by 10.216.182.6 with HTTP; Fri, 9 Jul 2010 04:08:57 -0700 (PDT) In-Reply-To: <1FF6659CB8948640A0694C9954BB5A392336BD31FF@pandora.tk.informatik.tu-darmstadt.de> References: <1FF6659CB8948640A0694C9954BB5A392336BD31FF@pandora.tk.informatik.tu-darmstadt.de> Date: Fri, 9 Jul 2010 07:08:57 -0400 Message-ID: Subject: Re: Process an aggregate with CAS multiplier and merger From: Eddie Epstein To: user@uima.apache.org Content-Type: text/plain; charset=ISO-8859-1 X-Virus-Checked: Checked by ClamAV on apache.org The CPE has no support for components returning new CASes. No need for a CPE, just put the collection reader inside the aggregate too. Eddie On Fri, Jul 9, 2010 at 5:10 AM, Torsten Zesch wrote: > Hi, > > I have a situation in which I want to split a document into several CASes, do some processing, and then merge the results back into a single result CAS. > > I implemented a CAS multiplier and a CAS merger that I put into an aggregate with a FixedFlow, setting ActionAfterCasMultiplier to "drop" and setting outputsNewCASes to "true" for the aggregate. > This should drop the source CAS and let the merged CAS be output by the aggregate. > > Now, if I run that aggregate in an CPE and put the consumer behind the aggregate, > => Reader + Aggregate[Multiply-Process-Merge] + Consumer > the consumer only sees the source CAS. > > However, if I put the consumer inside the Aggregate, > => Reader + Aggregate[Multiply-Process-Merge-Consumer] > the output is correct. > This means the mergedCAS is correctly created, but it is not available after the aggregate. > > Do I need to always put everything inside one big aggregate, or is there some way to also run pipelines like > => Reader + Process + Aggregate[Multiply-Process-Merge] + Process + Consumer > > Thanks, > Torsten >