[
https://issues.apache.org/jira/browse/SOLR-13973?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17190711#comment-17190711
]
Tim Allison commented on SOLR-13973:
------------------------------------
[~mkalkbrenner] I've been thinking about adding an "indexer" endpoint to Tika.
You'd configure your Solr/ES connection info and error handling choices via
json at startup and then send the bytes to tika-server's /indexer endpoint. It
would parse the file and forward the result to Solr. Would that simplify
anything?
I'm thoroughly on board with "don't break the user experience", but we've got
to get Tika out of Solr's jvm.
> Deprecate Tika
> --------------
>
> Key: SOLR-13973
> URL: https://issues.apache.org/jira/browse/SOLR-13973
> Project: Solr
> Issue Type: Improvement
> Reporter: Ishan Chattopadhyaya
> Assignee: 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
