You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tika.apache.org by "Tim Allison (Jira)" <ji...@apache.org> on 2021/05/01 11:22:00 UTC
[jira] [Commented] (TIKA-3377) Remove pipes components from
TikaConfig in 2.x
[ https://issues.apache.org/jira/browse/TIKA-3377?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17337785#comment-17337785 ]
Tim Allison commented on TIKA-3377:
-----------------------------------
[~zxxz] [~ndipiazza] I think I finally turned a corner on this... in a good way. A bunch more remains but this is where I was headed...no more h2. Please take a look and let me know what you think.
> Remove pipes components from TikaConfig in 2.x
> ----------------------------------------------
>
> Key: TIKA-3377
> URL: https://issues.apache.org/jira/browse/TIKA-3377
> Project: Tika
> Issue Type: Task
> Reporter: Tim Allison
> Assignee: Tim Allison
> Priority: Major
>
> I initially put pipes components in TikaConfig 2.x. I now think it would be better to have them specified in a tika-config.xml file, but actually loaded outside of TikaConfig. The reason is that not every jvm in a pipes process needs a fetcher, an emitter and a fetchiterator. Some of these components can be heavy, and there's no need to load them all in every jvm that reads a TikaConfig.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)