[
https://issues.apache.org/jira/browse/SOLR-7632?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17705138#comment-17705138
]
Jan Høydahl commented on SOLR-7632:
-----------------------------------
Following a [DISCUSS
thread|https://lists.apache.org/thread/lbm6wb88gd1cfktgs6sfvw5xf73o8trd] on dev
I'm working on a POC for this, in a hope to get rid Solr distribuion of the
weight, complexity and inflexibility of bundled Tika.
I already have code that forwards the input stream to Tika-Server and receives
and parses the JSON response of the parsed doc. Will post a PR eventually.
Once extraction module no longer depends on all the tika parsers, we can also
move XLSXResponseWriter (depending on POI) out to a separate module.
> 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
> Priority: Major
> Labels: gsoc2017, memex
>
> 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
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscr...@solr.apache.org
For additional commands, e-mail: issues-h...@solr.apache.org
