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] Closed: (UIMA-1245) Processing order of parent CAS different on UIMA and UIMA AS
Date Tue, 14 Apr 2009 16:22:15 GMT

     [ https://issues.apache.org/jira/browse/UIMA-1245?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Jerry Cwiklik closed UIMA-1245.
-------------------------------

    Resolution: Fixed

> 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
>            Assignee: 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