Hi Eddie,
thanks for the information. I wasn't aware that I couldn't use the Cas
Multiplier in a CPM. If I understand you right, the by "released" you mean that
the original CAS is passed on in the processing pipeline after hasNest()=false.
I guess I will have a closer look at the flow controller + aggregate now.
Eddie Epstein schrieb:
A CAS multiplier has the ability to create new CASes; one input CAS could be
used to create many, or many input CASes used to create one. An input CAS
cannot be "swallowed" by a CM; it is considered to be released when the CM
returns hasNext()=false.
A flow controller would be the best way to remove a CAS from the flow. If
you are using the CPM to construct your processing pipeline, note that it
does not support the CM either. Why not use an aggregate to assemble all
your components, which would enable use of a flow controller?
Eddie
On Thu, May 8, 2008 at 8:46 AM, Christoph Büscher <
[EMAIL PROTECTED]> wrote:
Hi,
just a short question concerning the correct use of a CAS Multiplier in
UIMA. As I understand it's usually the job of a CAS Multiplier to split
CASes into multiple parts/segments. Is it also an acceptable behaviour for
such a component to output no CAS at all when certain conditions are met? Or
does the framework complain or will behave strangely if a CAS enters the
Multiplier but never passes it?
I'm trying remove documents that meet a certain condition from the flow
completely. I don't want to use a Flow Controller because I don't have an
Aggregate to add it to.
Thanks,
--
--------------------------------
Christoph Büscher
--
--------------------------------
Christoph Büscher
