uima-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jerry Cwiklik (JIRA)" <uima-...@incubator.apache.org>
Subject [jira] Commented: (UIMA-1391) Client of a CAS Multiplier should be able to stop processing of a CAS
Date Wed, 01 Jul 2009 19:35:47 GMT

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

Jerry Cwiklik commented on UIMA-1391:

Modified client code to handle a new message type returned from a remote Cas Multiplier. When
a client sends an input CAS, the Cas Multiplier service immediately returns a ServiceInfo
message that contains this service FreeCas Notification queue. This queue is unique to the
service. It is this queue that will receive notifications from the client. Currently the client
can send FreeCas and Stop requests. This change enables scaleout of remote Cas Multipliers.
The client now knows which instance processes each 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.

View raw message