You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tika.apache.org by "Jukka Zitting (Created) (JIRA)" <ji...@apache.org> on 2012/03/27 17:48:26 UTC
[jira] [Created] (TIKA-884) Dynamic loading of Parser and Detector
services
Dynamic loading of Parser and Detector services
-----------------------------------------------
Key: TIKA-884
URL: https://issues.apache.org/jira/browse/TIKA-884
Project: Tika
Issue Type: Improvement
Affects Versions: 1.1
Reporter: Jukka Zitting
Assignee: Jukka Zitting
When deployed in an OSGi container, calling {{new Tika()}} will dynamically load all available {{Parser}} and {{Detector}} services. This works fine for the typical use case where the facade instance is only used for a single specific task (parsing a single document, etc.).
However, if a client instead uses a singe, long-lived Tika instance, the list of referenced services never gets updated even if the set of services in the container changes over time. To address this problem we should make Tika reload the set of available services each time they're needed. The performance overhead of doing this should be minimal compared to the typical parsing or type detection tasks.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Resolved] (TIKA-884) Dynamic loading of Parser and Detector
services
Posted by "Jukka Zitting (Resolved) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/TIKA-884?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jukka Zitting resolved TIKA-884.
--------------------------------
Resolution: Fixed
Fix Version/s: 1.2
Fixed in revision 1305920.
> Dynamic loading of Parser and Detector services
> -----------------------------------------------
>
> Key: TIKA-884
> URL: https://issues.apache.org/jira/browse/TIKA-884
> Project: Tika
> Issue Type: Improvement
> Affects Versions: 1.1
> Reporter: Jukka Zitting
> Assignee: Jukka Zitting
> Labels: OSGi
> Fix For: 1.2
>
>
> When deployed in an OSGi container, calling {{new Tika()}} will dynamically load all available {{Parser}} and {{Detector}} services. This works fine for the typical use case where the facade instance is only used for a single specific task (parsing a single document, etc.).
> However, if a client instead uses a singe, long-lived Tika instance, the list of referenced services never gets updated even if the set of services in the container changes over time. To address this problem we should make Tika reload the set of available services each time they're needed. The performance overhead of doing this should be minimal compared to the typical parsing or type detection tasks.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira