No, the issue is still open.
When I start working on one of the issues that are still recorded on Google
Code, I open a corresponding issue on the Apache Jira and add a link to each of
them, pointing to each other. I also set the ASFJira flag on the Google Code
tracker to true.
-- Richard
Option 1 - by foot:
I guess the uimaFIT JCasIterator should continue to read CAS by CAS
from the reader. However, for each CAS read by the reader, it should be
able to return 0-x CASes. Currently it can only return 1 because it
calls engine.process(jCas) on each engine in turn. To return 0-x,
Option 2 - let UIMA do the heavy lifting
An alternative and much simple approach might be to create an aggregate which
does not only contain the engines, but also the reader. Then you don't have
to
worry about the reader anymore at all. Just create a UIMA JCasIterator and
poll CASes
For further reference:
https://issues.apache.org/jira/browse/UIMA-3470
-- Richard
On 22.11.2013, at 07:37, Richard Eckart de Castilho r...@apache.org wrote:
I believe the JCasIterable is currently implemented as a loop which calls
process on the analysis engines for every CAS produced by the
I believe the JCasIterable is currently implemented as a loop which calls
process on the analysis engines for every CAS produced by the reader
and then returns the corresponding CAS. This wouldn't work with multipliers.
Can you please file an issue in the Apache Jira, preferrably with a minimal
I have successfully used CasMultiplier to spilt up a document into segments
for further processing using SimplePipeline.runPipeline().
I did this by wrapping the CasMultiplier and the succeeding Annotator within a
aggregate.
But by simply changing the usage of SimplePipeline.runPipeline() to
