jackrabbit-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jukka Zitting (JIRA)" <j...@apache.org>
Subject [jira] [Resolved] (JCR-2864) Use out-of-process text extraction
Date Tue, 12 Apr 2011 14:57:06 GMT

     [ https://issues.apache.org/jira/browse/JCR-2864?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel

Jukka Zitting resolved JCR-2864.

    Resolution: Fixed

I've implemented this by adding a new "forkJavaCommand" configuration option. When specified,
this command will be used to fork background text extraction processes up to the configured
"extractorPoolSize" limit (by default 2 x processor count). The pool size limit will only
become effective once we upgrade to Tika 1.0 where TIKA-639 is implemented.

The fork memory use issue is best handled within the Tika issue.

> Use out-of-process text extraction
> ----------------------------------
>                 Key: JCR-2864
>                 URL: https://issues.apache.org/jira/browse/JCR-2864
>             Project: Jackrabbit Content Repository
>          Issue Type: Improvement
>          Components: indexing, jackrabbit-core
>            Reporter: Jukka Zitting
>            Assignee: Jukka Zitting
>             Fix For: 2.3.0
> The upcoming Tika 0.9 release will contain a highly useful out-of-process text extraction
feature (TIKA-416) that we should use also in Jackrabbit.

This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

View raw message