uima-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Joern Kottmann (JIRA)" <...@uima.apache.org>
Subject [jira] [Commented] (UIMA-1970) Reload updated resources while an analysis pipeline is running
Date Wed, 07 Sep 2016 11:34:20 GMT

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

Joern Kottmann commented on UIMA-1970:

For example: UIMA-AS is capable of running pipelines for a longer period of tme, it could
from time to time reinitialize them and as part of that refresh remote resources.

> Reload updated resources while an analysis pipeline is running
> --------------------------------------------------------------
>                 Key: UIMA-1970
>                 URL: https://issues.apache.org/jira/browse/UIMA-1970
>             Project: UIMA
>          Issue Type: New Feature
>          Components: Core Java Framework
>    Affects Versions: 2.3.1SDK
>            Reporter: Joern Kottmann
>              Labels: Resources
> In many use cases resources used by Analysis Engine are updated more frequently than
the AE implementation.
> Samples of such resources are huge dictionaries which are extended with new names on
a daily basis
> or statistical models which are re-trained frequently to be adjusted to data from the
past minutes.  
> For a resource updates an analysis pipeline has to be stopped and started manually to
pick up the updated resource.
> It would be nice if the framework could automate this procedure. In order to do that
it must have a capability to detect
> updated resources and perform the re-initialization of affected Analysis Engines.
> If the pipelines run multiple instances of these Analysis Engines it would be nice if
a rolling
> update could be performed in a way that the processing of CASes never comes to an halt.
> That should be handled in different issues for the CPE and UIMA-AS. 

This message was sent by Atlassian JIRA

View raw message