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-1245) Processing order of parent CAS different on UIMA and UIMA AS
Date Tue, 17 Feb 2009 14:45:01 GMT

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

Jerry Cwiklik commented on UIMA-1245:
-------------------------------------

It seems that the general agreement is that the CM should hold the input CAS until ALL of
its children are processed. Only than, the input CAS would be returned to the client. This
would be a default. To override this, the user would add a new attribute in the dd for the
Cas Multiplier . Eddie votes for processParentEarly="true".  If this is provided , the parent
CAS would be returned from the CM as soon as all children are generated. This would enable
processing of input CAS and its children at the same time. The input CAS would still be held
in the final state until all its children are processed. Assuming everyone agrees, I need
Marshall to modify dd2spring to support the new CM parameter. 

> Processing order of parent CAS different on UIMA and UIMA AS
> ------------------------------------------------------------
>
>                 Key: UIMA-1245
>                 URL: https://issues.apache.org/jira/browse/UIMA-1245
>             Project: UIMA
>          Issue Type: Bug
>          Components: Async Scaleout
>            Reporter: Eddie Epstein
>
> Arron Kaplan raised the question of when parent CASes are processed relative to their
children. See http://markmail.org/message/5cop7iv2nshouhgs  As of now, the processing order
for a multi-threaded UIMA AS aggregate is different than that for a single-threaded UIMA aggregate.
> A discussion with Burn, Adam, Jerry, Marshall and myself concluded that the default processing
order for UIMA AS should be changed to be the same as in UIMA, in order to have the same application
behavior for both. This will be done by suspending flow of a parent CAS after it is returned
from a CasMultiplier delegate until all its children CASes have finished processing.
> However, there also needs to be a UIMA AS deployment option for CasMultiplier delegates
that allows the parent CAS to resume processing immediately after being returned from the
CM. This option is needed to enable parallel processing.

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


Mime
View raw message