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 2017/11/29 21:39:00 UTC
[jira] [Created] (TIKA-2514) Create alternate ForkParser that
doesn't require serialization
Tim Allison created TIKA-2514:
---------------------------------
Summary: Create alternate ForkParser that doesn't require serialization
Key: TIKA-2514
URL: https://issues.apache.org/jira/browse/TIKA-2514
Project: Tika
Issue Type: Improvement
Reporter: Tim Allison
The ForkParser is a great option for handling oom/permanent hangs; and from a code/design perspective, IMHO, it is a thing of beauty.
On the user list [~JimIdle], recently pointed out that the ForkParser can't work with custom parsers that depend on non-serializable components.
It would be great to allow users to specify a TIKA_HOME variable or pass in a directory with the tika-related jars and run the server as a separate process with that dir as the class path. This would also make adding optional jars much easier and could prevent jar hell with the calling application.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)