Hi Robert, First, I’d check if your collection doesn’t pick up a different config set. The collection view under Cloud in SolrAdmin - each collection will include the configset it's linked to. You may also want to check if configoverlay.json was created in the conf/directory, it may have overshadowed the solrconfig.
Thank you, Patryk On 2026/01/28 11:09:01 Ehrenleitner Robert Harald wrote: > Hi, > > I have a Solr core called plus-documents-dev whose solrconfig.xml contains > this stanza: > > <requestHandler name="/update/extract" > class="solr.extraction.ExtractingRequestHandler$ > <lst name="defaults"> > <str name="lowernames">true</str> > <str name="fmap.content">content</str> > <str name="extraction.backend">tikaserver</str> > <str name="tikaserver.url">http://localhost:9998</str> > </lst> > </requestHandler> > > However, when running the crawler, I can see this in the logs of Solr: > > 2026-01-28 10:20:36.696 INFO (qtp1991278377-35-null-13) [ > x:plus-documents-dev] o.a.s.c.PluginBag Going to create a new requestHandler > with {type = requestHandler,name = /update/extract,class = > solr.extraction.ExtractingRequestHandler,attributes = {name=/update/extract, > class=solr.extraction.ExtractingRequestHandler, startup=lazy, > defaults={lowernames=true}},args = {startup=lazy, defaults={lowernames=true, > df=_text_}}} > 2026-01-28 10:20:36.999 WARN (qtp1991278377-35-null-13) [ > x:plus-documents-dev] o.a.s.D.Local Tika The 'local' extraction backend is > deprecated > > And Tika does not log anything. So, it looks like Solr > > * > Falls back to the deprecated in-process Tika extractor > * > And completely ignores what I have written in fmap.content > > So, I assume Solr actually ignores the whole stanza. > > Tika is listening properly: > > # ss -tulpn | grep ':9998' > tcp LISTEN 0 50 *:9998 *:* > users:(("java",pid=1886775,fd=8)) > > Kind regards, > > > Mag.phil. Robert Ehrenleitner, BEng. > University of Salzburg > >
