You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tika.apache.org by "Bob Paulin (JIRA)" <ji...@apache.org> on 2015/10/15 03:35:05 UTC

[jira] [Updated] (TIKA-1762) Create Executor Service from TikaConfig

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

Bob Paulin updated TIKA-1762:
-----------------------------
    Description: 
Create a configurable executor service that is configurable from the TikaConfig.

 Konstantin Gribov added a comment - 23/Sep/15 09:55

Bob Paulin, I have two ideas on the issue:

    by default use common thread pool, configured via and contained in TikaConfig as Tyler Palsulich suggested,
    you can pass thread pool for parser invocation via ParserContext with fallback to default if now thread pool/executor service in context.

Also o.a.tika.Tika#parse(InputStream, Metadate) produces o.a.tika.parser.ParsingReader and anonymous Executor with unbounded daemon thread creation.


  was:Create a configurable executor service that is configurable from the TikaConfig.


> Create Executor Service from TikaConfig
> ---------------------------------------
>
>                 Key: TIKA-1762
>                 URL: https://issues.apache.org/jira/browse/TIKA-1762
>             Project: Tika
>          Issue Type: Improvement
>            Reporter: Bob Paulin
>             Fix For: 1.11
>
>
> Create a configurable executor service that is configurable from the TikaConfig.
>  Konstantin Gribov added a comment - 23/Sep/15 09:55
> Bob Paulin, I have two ideas on the issue:
>     by default use common thread pool, configured via and contained in TikaConfig as Tyler Palsulich suggested,
>     you can pass thread pool for parser invocation via ParserContext with fallback to default if now thread pool/executor service in context.
> Also o.a.tika.Tika#parse(InputStream, Metadate) produces o.a.tika.parser.ParsingReader and anonymous Executor with unbounded daemon thread creation.



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