lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Cassandra Targett (JIRA)" <>
Subject [jira] [Commented] (SOLR-12423) Upgrade to Tika 1.19.1 when available
Date Thu, 25 Oct 2018 16:39:00 GMT


Cassandra Targett commented on SOLR-12423:

This is marked as Fixed for 7.6, and the issue appears in CHANGES under 7.6, but the version
listed under "Versions of Major Components" still lists 1.18 as the Tika version, while the
same section under 8.0 lists 1.19.1.

This seems like a simple oversight, but [~erickerickson], [], any specific
reason why I shouldn't just fix that?

> Upgrade to Tika 1.19.1 when available
> -------------------------------------
>                 Key: SOLR-12423
>                 URL:
>             Project: Solr
>          Issue Type: Task
>      Security Level: Public(Default Security Level. Issues are Public) 
>            Reporter: Tim Allison
>            Assignee: Erick Erickson
>            Priority: Major
>             Fix For: 7.6, master (8.0)
>         Attachments: SOLR-12423.patch
>          Time Spent: 50m
>  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 issue covers the basic upgrading to 1.19.1.  For the migration to the ForkParser,
see SOLR-11721.

This message was sent by Atlassian JIRA

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message