[
https://issues.apache.org/jira/browse/UIMA-925?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Eddie Epstein closed UIMA-925.
------------------------------
Resolution: Fixed
Thanks Jerry. Nice to have this fixed for the first release.
> How does a UIMA-AS client using sendCAS associate a returned error with the
> CAS that caused it?
> -----------------------------------------------------------------------------------------------
>
> Key: UIMA-925
> URL: https://issues.apache.org/jira/browse/UIMA-925
> Project: UIMA
> Issue Type: Bug
> Components: Async Scaleout
> Affects Versions: 2.2.1
> Reporter: Burn Lewis
> Priority: Minor
> Fix For: 2.2.2S
>
> Attachments: uimaj-as-activemq-UIMA-925-patch.txt,
> uimaj-as-core-UIMA-925-patch.txt, uimaj-as-jms-UIMA-925-patch.txt
>
>
> When using the UIMA-AS client 'sendCAS' api a unique ID is returned but there
> is no explanation of how this may be used. When an error is returned to the
> UimaASStatusCallbackListener there does not appear to be a way to tell from
> the EntityProcessStatus which of the input CASes failed. Since they are sent
> asynchronously they and their errors may be returned out of order.
> void entityProcessComplete ( org.apache.uima.cas.CAS aCas,
> org.apache.uima.collection.EntityProcessStatus aStatus )
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
