You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@uima.apache.org by "Eddie Epstein (JIRA)" <ui...@incubator.apache.org> on 2008/10/24 17:29:44 UTC
[jira] Created: (UIMA-1212) Optimize indexRepository methods
getIndexedFS and flush
Optimize indexRepository methods getIndexedFS and flush
-------------------------------------------------------
Key: UIMA-1212
URL: https://issues.apache.org/jira/browse/UIMA-1212
Project: UIMA
Issue Type: Improvement
Components: Core Java Framework
Reporter: Eddie Epstein
Assignee: Eddie Epstein
The getIndexedFS and flush methods currently iterate over all defined indexes. When the number of indexes is large, for example when there are many annotation types defined, this overhead becomes significant relative to lightweight annotator processing. By marking which indexes are actually used, it is possible to eliminate most of the overhead.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Closed: (UIMA-1212) Optimize indexRepository methods
getIndexedFS and flush
Posted by "Eddie Epstein (JIRA)" <ui...@incubator.apache.org>.
[ https://issues.apache.org/jira/browse/UIMA-1212?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Eddie Epstein closed UIMA-1212.
-------------------------------
Resolution: Fixed
> Optimize indexRepository methods getIndexedFS and flush
> -------------------------------------------------------
>
> Key: UIMA-1212
> URL: https://issues.apache.org/jira/browse/UIMA-1212
> Project: UIMA
> Issue Type: Improvement
> Components: Core Java Framework
> Reporter: Eddie Epstein
> Assignee: Eddie Epstein
>
> The getIndexedFS and flush methods currently iterate over all defined indexes. When the number of indexes is large, for example when there are many annotation types defined, this overhead becomes significant relative to lightweight annotator processing. By marking which indexes are actually used, it is possible to eliminate most of the overhead.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (UIMA-1212) Optimize indexRepository methods
getIndexedFS and flush
Posted by "Marshall Schor (JIRA)" <ui...@incubator.apache.org>.
[ https://issues.apache.org/jira/browse/UIMA-1212?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Marshall Schor updated UIMA-1212:
---------------------------------
Fix Version/s: 2.3
> Optimize indexRepository methods getIndexedFS and flush
> -------------------------------------------------------
>
> Key: UIMA-1212
> URL: https://issues.apache.org/jira/browse/UIMA-1212
> Project: UIMA
> Issue Type: Improvement
> Components: Core Java Framework
> Reporter: Eddie Epstein
> Assignee: Eddie Epstein
> Fix For: 2.3
>
>
> The getIndexedFS and flush methods currently iterate over all defined indexes. When the number of indexes is large, for example when there are many annotation types defined, this overhead becomes significant relative to lightweight annotator processing. By marking which indexes are actually used, it is possible to eliminate most of the overhead.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.