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 Wed, 25 Feb 2009 14:33:03 GMT

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

Jerry Cwiklik commented on UIMA-1245:

After the last round of discussions here is *my* understanding how things should work:

1) In both remote and colocated case, the input CAS will *not* be held in the primitive CM.
The input CAS will immediately follow its last child.

2) The aggregate will hold the input CAS (if configured to do so) until all its children *leave*
the aggregate. This is in contrast with the other idea where the CAS was to be held until
all its children were processed in all aggregates. The latter requires complicated notification
mechanism. As I understand it we opt for a simpler solution, which is the former. 
The aggregate will decrement the input CAS child count as soon as the child CAS is either
dropped in the aggregate or the child CAS is sent to the aggregate's client. As soon as the
child count hits zero, the input CAS will be allowed to continue to the next step in the flow.

3) The parameter processParentLast will be defined on the containing aggregate not individual
CM. Is this reasonable? 

> 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.

View raw message