[
https://issues.apache.org/jira/browse/SOLR-13973?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17216695#comment-17216695
]
David Smiley commented on SOLR-13973:
-------------------------------------
I don't think we should deprecate this because it is important enough for our
users. Telling a user "Deprecated" tells them to use something else, but there
are no ready-made alternatives. Two options: SOLR-7632 (external Tika server)
or moving this to a 3rd party "package" will address the user need. Tim, if
you want to do the latter, I can help.
Given that we have an active committer here maintaining
ExtractingRequestHandler (Tim Allison), I'm not sure why we need to remove it
from Solr altogether. My chief complaint is all those JARs adding weight to a
default distribution, but that's solveable either by SOLR-7632 (which addresses
the same-JVM issue as well), or by the "slim Solr" contrib proposal of
Ishan/Noble.
> 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
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> 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: issues-unsubscr...@lucene.apache.org
For additional commands, e-mail: issues-h...@lucene.apache.org
