You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@lucene.apache.org by "Tim Allison (JIRA)" <ji...@apache.org> on 2018/10/01 13:00:00 UTC
[jira] [Commented] (SOLR-12423) Upgrade to Tika 1.19.1 when
available and refactor to use the ForkParser
[ https://issues.apache.org/jira/browse/SOLR-12423?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16633961#comment-16633961 ]
Tim Allison commented on SOLR-12423:
------------------------------------
Tika 1.19 fixed a number of vulnerabilities (https://tika.apache.org/security.html), but it has some issues. We should wait for 1.19.1. We'll be rolling rc2 as soon as PDFBox 2.0.12 is available, and the voting for PDFBox 2.0.12 should start today.
> Upgrade to Tika 1.19.1 when available and refactor to use the ForkParser
> ------------------------------------------------------------------------
>
> Key: SOLR-12423
> URL: https://issues.apache.org/jira/browse/SOLR-12423
> Project: Solr
> Issue Type: Task
> Security Level: Public(Default Security Level. Issues are Public)
> Reporter: Tim Allison
> Priority: Major
> Time Spent: 0.5h
> Remaining Estimate: 0h
>
> In Tika 1.19, there will be the ability to call the ForkParser and specify a directory of jars from which to load the classes for the Parser in the child processes. This will allow us to remove all of the parser dependencies from Solr. We’ll still need tika-core, of course, but we could drop tika-app.jar in the child process’ bin directory and be done with the upgrade... no more fiddly dependency upgrades and threat of jar hell.
>
> The ForkParser also protects against ooms, infinite loops and jvm crashes. W00t!
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org