You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@uima.apache.org by "Peter Klügl (JIRA)" <de...@uima.apache.org> on 2016/01/14 11:19:39 UTC

[jira] [Commented] (UIMA-4568) Ruta: improve internal indexing for multiple ruta engine calls

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

Peter Klügl commented on UIMA-4568:
-----------------------------------

The approach right now based on custom fields in a JCas cover class actually works. The problem was caused by the change of the classloader which removed all instances and enforced the complete reindexing in ruta initialization. I will add a new configuration parameter for restricting the annotations to be reindexed. This should do for UIMA-4484

> Ruta: improve internal indexing for multiple ruta engine calls
> --------------------------------------------------------------
>
>                 Key: UIMA-4568
>                 URL: https://issues.apache.org/jira/browse/UIMA-4568
>             Project: UIMA
>          Issue Type: Improvement
>          Components: ruta
>    Affects Versions: 2.2.1ruta
>            Reporter: Peter Klügl
>            Assignee: Peter Klügl
>
> Right now, the RutaBasics are not cached in the CAS. Therefore, all the internal information in beginMap, endMap and partof needs to be recreated for each call of an Ruta analysis engine. Investigate how this problem can be solved or relaxed.
> Some ideas (brainstorming):
> - wait until annotations in UIMA are represented by a normal java objects
> - try to enforce caching the relevant FSs (RutaBasic)
> - store the information in features (the normal CAS way)
> - add an extra index (can it be injected in order to avoid the problems with type priorities?)
> - use an external resource (the probably most unnatural way)



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)