Hey Eddie, thanks again! :-)
So the idea is that the work item is the CAS that the CR sent to the CM, right?
The work item CAS consists of a list of artifacts which are output by the CM,
processed by the pipeline and finally cached by the CC.
Then, I can somehow (have to read this up) have the w
Hi Erik,
There is a brief discussion of this in the duccbook in section 9.3 ...
https://uima.apache.org/d/uima-ducc-2.2.2/duccbook.html#x1-1880009.3
In particular, the 3rd option, "Flushing cached data". This assumes that
the batch of work to be flushed is represented by each workitem CAS.
Regar
We have developed a framework to deal with UIMA AS programmatically. No dealing
with XML ever.
Feel free to check it out:
http://department-of-veterans-affairs.github.io/Leo/
Olga
-Original Message-
From: on behalf of Jaroslaw Cwiklik
Reply-To: "user@uima.apache.org"
Date: Tuesday
Thanks Jerry, not sure how I missed that.
-John
From: uim...@gmail.com [uim...@gmail.com] on behalf of Jaroslaw Cwiklik
[cwik...@apache.org]
Sent: Tuesday, May 15, 2018 3:58 AM
To: user@uima.apache.org
Subject: [External Sender] Re: Deploy Async Service
And another question concerning DUCC :-)
With my CPEs I use a lot the batchProcessingComplete() and
collectionProcessingComplete() methods. I need them because I do a lot of
database interactions where I need to send data in batches due to the overhead
of network communication.
How is that hand
You can generate UIMA-AS deployment descriptor programmatically. You still
need AE descriptor though.
Please check UIMA-AS documentation:
https://uima.apache.org/d/uima-as-2.10.3/uima_async_scaleout.html#ugr.ref.async.api.usage
section 4.10 Generating Deployment Descriptor Programmatically
Jerry
