[
https://issues.apache.org/jira/browse/SOLR-7632?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14572729#comment-14572729
]
Erik Hatcher commented on SOLR-7632:
------------------------------------
[~chrismattmann] wait, don't close "won't fix" so fast! I think this would be
a nice addition, but as an option such that /update/extract would use Tika
embedded by default or when configured to do so, send the documents to
Tika-Server.
Out of curiosity, can Tika-Server forward it's processed output instead of
sending back to the posting client? If so, then one could put Tika-Server
between a client and Solr without the client having to send to Tika-Server, get
the results, package them up, and send to Solr.
> Change the ExtractingRequestHandler to use Tika-Server
> ------------------------------------------------------
>
> Key: SOLR-7632
> URL: https://issues.apache.org/jira/browse/SOLR-7632
> Project: Solr
> Issue Type: Improvement
> Components: contrib - Solr Cell (Tika extraction)
> Reporter: Chris A. Mattmann
>
> It's a pain to upgrade Tika's jars all the times when we release, and if Tika
> fails it messes up the ExtractingRequestHandler (e.g., the document type
> caused Tika to fail, etc). A more reliable way and also separated, and easier
> to deploy version of the ExtractingRequestHandler would make a network call
> to the Tika JAXRS server, and then call Tika on the Solr server side, get the
> results and then index the information that way. I have a patch in the works
> from the DARPA Memex project and I hope to post it soon.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
