[
https://issues.apache.org/jira/browse/SOLR-13973?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17158639#comment-17158639
]
Tim Allison edited comment on SOLR-13973 at 7/15/20, 7:15 PM:
--------------------------------------------------------------
I've been toying with adding a forwarding capability to tika-server
(TIKA-3093). So, if you curl a document to tika-server {{/tika2solr}}, we'd
use our tika parsing stuff in tika-server and the extracted text to Solr. This
would keep the dangerous part (tika parsing a document) out of the client code.
was (Author: [email protected]):
I've been toying with adding a forwarding capability to tika-server. So, if
you curl a document to tika-server {{/tika2solr}}, we'd use our tika parsing
stuff in tika-server and the extracted text to Solr. This would keep the
dangerous part (tika parsing a document) out of the client code.
> Deprecate Tika
> --------------
>
> Key: SOLR-13973
> URL: https://issues.apache.org/jira/browse/SOLR-13973
> Project: Solr
> Issue Type: Improvement
> Reporter: Ishan Chattopadhyaya
> Priority: Blocker
> Fix For: 8.7
>
>
> Solr's primary responsibility should be to focus on search and scalability.
> Having to deal with the problems (CVEs) of Velocity, Tika etc. can slow us
> down. I propose that we deprecate it going forward.
> Tika can be run outside Solr. Going forward, if someone wants to use these,
> it should be possible to bring them into third party packages and installed
> via package manager.
> Plan is to just to throw warnings in logs and add deprecation notes in
> reference guide for now. Removal can be done in 9.0.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
