[
https://issues.apache.org/jira/browse/TIKA-1762?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14958796#comment-14958796
]
Nick Burch commented on TIKA-1762:
----------------------------------
I'm wondering if the Parser Context is the right place for this? Is it
generally something you'd want to change on a per-document basis?
I don't know if this would work, but since most of the parsers which would want
the pool will come via TikaConfig, how about:
* Thread Pool created by Tika Config, based on defaults or explicit config
(defaults a moderate size)
* Tika Config gives that (directly? wrapped as executor service?) to external
parsers it creates
* Have constructor for those externals parsers which take both Tika Config and
a direct executor service, and get it from that
* If you create an external parser yourself, and don't set a config or the
service, it picks a much smaller default
> 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)
