[jira] Commented: (UIMA-1391) Client of a CAS Multiplier should be able to stop processing of a CAS

["Jerry Cwiklik (JIRA)" <ui...@incubator.apache.org>]

    [ https://issues.apache.org/jira/browse/UIMA-1391?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12725641#action_12725641 ] 

Jerry Cwiklik commented on UIMA-1391:
-------------------------------------

Extended Uima AS client API to support two new methods:

	  public void stopProducingCases();

	  public void stopProducingCases(String aCasReferenceId);

The first will iterate over all outstanding CASes sending a stop request for each to a service.  The second will send a stop request to a service for a specific CAS.  In either case, the service propagates Stop request to all its Cas Multipliers waiting for CASes to finish before returning an input CAS.  Both methods are asynchronous, meaning that the request to stop is sent and the control returns back to the application. The confirmation of a stop is receipt of a input CAS.

> Client of a CAS Multiplier should be able to stop processing of a CAS
> ---------------------------------------------------------------------
>
>                 Key: UIMA-1391
>                 URL: https://issues.apache.org/jira/browse/UIMA-1391
>             Project: UIMA
>          Issue Type: Improvement
>          Components: Async Scaleout
>            Reporter: Burn Lewis
>             Fix For: 2.3S
>
>
> Normally the number of CASes generated by a Cas Multiplier is determined by the CM itself, but with an aggregate CM that number may be hard to anticipate or control.  Some applications may not need all of the generated CASes ... they may be satisfied once an appropriate amount of information has been returned.
> Hence it would be convenient for the client to be able to request that the CM stop generating CASes, and if an aggregate, stop processing any internal CASes generated from the input CAS.  Such a request is probably only useful for CMs acting as pure segmenters ... if the CM is merging CASes or resegmenting them then the process could be terminated by the application upon receiving an end-of-stream CAS.  It might be an acceptable simplification to have the stop request stop all processing of active CASes, but then again it may be easily handled by the changes being made to stop an aggregate CM when a generated CAS produces an exception.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.