Tika extraction failing on your index, from Drupal or from your own code? Four things to check, in the order that resolves most cases.
01 · Try a different Solr version
Before reading logs, create a new Opensolr index on Solr 9, or on 7, 6 or 5. Avoid Solr 8.x: its Jetty version has known issues that show up as Tika failures. Create a new Opensolr index and point your integration at it to confirm.
02 · Make sure Tika is enabled in your region
Tika is not present in every environment. If you suspect it is missing, contact Opensolr support and we will enable it for your index and region.
03 · Confirm the handler in solrconfig.xml
Your solrconfig.xml needs the extraction request handler defined:
<requestHandler name="/extract/tika" class="org.apache.solr.handler.extraction.ExtractingRequestHandler" startup="lazy"> <lst name="defaults"> </lst> <!-- This path only extracts - never updates --> <lst name="invariants"> <bool name="extractOnly">true</bool> </lst> </requestHandler>
With extractOnly set as an invariant, this path extracts text and never writes documents, so a misconfigured client cannot update your index by accident.
04 · Still failing
Send us the index name and the error
Contact support with the exact message you get back. Most Tika problems are a version mismatch between Solr and the client library, which is quick for us to confirm from our side.
Indexing remote files by URL
If the error mentions remote streaming rather than extraction, that is a different switch: see enabling remote streaming.