Thanks for your input.
To give some more information about our use case:
Our input is a mix of documents.
Only some of them are relevant and should be written by the consumer.
We also thought about the solution with a special FeatureStructure, but
this has the disadvantage that the consumer needs
Hi!
On Sun, Sep 06, 2015 at 10:58:44AM -0400, Eddie Epstein wrote:
> On Sun, Sep 6, 2015 at 10:11 AM, Petr Baudis wrote:
> > (ii) Use an internal "intermediary" CAS instance in process() to which
> > I append my sentences, then use it as a source of output CASes. Turns
> > out (surprisingly)
Keeping the filter inside the INNER may still be useful to
terminate any further processing in that AAE.
outputsNewCases=true is just saying that an aggregate is
a CasMultiplier and *might* return child-CASes. It doesn't
change the CAS-in/CAS-out contract for the component.
I think a fair amount
That would require that the OUTER_AAE is aware of the filtering.
We would prefer if all customization/filtering/etc. could be done in the
INNER_AAE which is the declared extension point.
In the worst case, we'd probably opt to move the FILTER from to
the OUTER_AAE entirely and make filtering a de
How about the filter adds a FeatureStructure indicating that the CAS should
be dropped.
Then when the INNER_AAE returns the CAS, the flow controller in the
OUTER_AAE
sends the CAS to FinalStep?
Eddie
On Sun, Sep 6, 2015 at 11:08 AM, Richard Eckart de Castilho
wrote:
> Eddie,
>
> we (Torsten and
Eddie,
we (Torsten and I) have the case that a reader produces a number of CASes
and we want to filter out some of them because they do not match a given
criteria.
The pipeline/flow structure we are using looks as follows:
READER -> OUTER_AAE { AEs..., INNER_AAE { FILTER }, AEs..., CONSUMER }
R
Richard,
In general the input CAS must continue down some processing path.
Where is it stored and what triggers its continued processing if it is not
returned?
Eddie
On Sun, Sep 6, 2015 at 10:28 AM, Richard Eckart de Castilho
wrote:
> Hi Eddie,
>
> in most cases, we use process(CAS) and in suc
Hi Petr
On Sun, Sep 6, 2015 at 10:11 AM, Petr Baudis wrote:
> Hi!
>
> I'm currently struggling to perform a complex flow transformation with
> UIMA. I have multiple (N) CASes with some fulltext search results.
> I chop these search results to sentences and would like to pick the top
> M sen
Hi Richard,
FinalStep() in a CasMultiplier aggregate means to stop further flow
in the aggregate and return the CAS to the component that passed
the CAS into the aggregate, or if a child-CAS, passed the child's
parent-CAS into the aggregate.
FinalStep(true) is used to stop a child-CAS from being
Hi Eddie,
in most cases, we use process(CAS) and in such a case what you describe
is very logical.
However, when setting outputsNewCases to true, doesn't the contract change?
My understanding is that processAndOutputNewCASes(CAS) is being
used and in such a case. Why shouldn't it be ok that the
Hi!
I'm currently struggling to perform a complex flow transformation with
UIMA. I have multiple (N) CASes with some fulltext search results.
I chop these search results to sentences and would like to pick the top
M sentences from the search results collected and build CASes from them
to do f
Hi Eddie,
ok, but why can input CASes created outside the aggregate not be dropped?
Cheers,
-- Richard
On 06.09.2015, at 15:58, Eddie Epstein wrote:
> Hi Torsten,
>
> The documentation says ...
>
> public FinalStep(boolean aForceCasToBeDropped)
>
> Creates a new FinalStep, and may indica
Hi Torsten,
The documentation says ...
public FinalStep(boolean aForceCasToBeDropped)
Creates a new FinalStep, and may indicate that a CAS should be dropped.
This can only be used for CASes that are produced internally to the
aggregate.
It is an error to attempt to drop a CAS that was p
13 matches
Mail list logo
