[
https://issues.apache.org/jira/browse/UIMA-1970?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15473186#comment-15473186
]
Richard Eckart de Castilho commented on UIMA-1970:
--------------------------------------------------
My understanding is that the way Jörg describes it "a way to update" is
basically a call to reinitialize(). That would leave the user to writing the
trigger code. If I imagine that, I end up with something like:
{noformat}
if (needsUpdate()) {
reinitialize();
}
{noformat}
This code seems so trivial that a user desiring an auto-updating resource could
easily put it into the resource itself. I don't see at the moment what useful
contribution the core UIMA framework could provide here.
> 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: Async Scaleout
> 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
(v6.3.4#6332)
