Thanks Shawn. The way we have it configured presently is as follows: 
icu4j.jar is located in /opt/solr/contrib/analysis-extras/lib/icu4j-62.1.jar

solrconfig.xml contains:

<lib dir="${solr.install.dir:../../../..}/contrib/analysis-extras/lib" 
regex=".*\.jar" />

Which should load the jar at startup, correct?


Is there anything significant about the mime-type error?

Expected mime type application/octet-stream but got text/html

Thanks,
Shane



-----Original Message-----
From: Shawn Heisey <apa...@elyograg.org> 
Sent: Sunday, August 9, 2020 3:00 AM
To: solr-user@lucene.apache.org
Subject: Re: Can create collections with Drupal 8 configset

On 8/8/2020 10:31 PM, Shane Brooks wrote:
> org.apache.solr.client.solrj.impl.HttpSolrClient$RemoteSolrException:E
> rror from server at http://192.168.xx.xx:8983/solr: Expected mime type 
> application/octet-stream but got text/html. <html>\n<head>\n<meta 
> http-equiv=\"Content-Type\"
> content=\"text/html;charset=utf-8\"/>\n<title>Error 500 Server 
> Error</title>\n</head>\n<body><h2>HTTP ERROR 500</h2>\n<p>Problem 
> accessing /solr/admin/cores. Reason:\n<pre> Server 
> Error</pre></p><h3>Caused by:</h3><pre>java.lang.NoClassDefFoundError:
> org/apache/lucene/collation/ICUCollationKeyAnalyzer\n\tat
>
>
> I haven't found anything on Google except that ICUCollationKeyAnalyzer 
> depends on the icu4j library, which I verified is part of the SOLR 
> package.

The icu4j library and the related Lucene jars for ICU capability are not 
part of Solr by default.  They can be found in the "contrib" in the Solr 
download ... but you must add the jars to Solr if you intend to use any 
contrib capability.

The best way I have found to add custom jars to Solr is to create a 
"lib" directory under the location designated as the solr home and place 
the jars there.  All jars found in that directory will be automatically 
loaded and will be available to all cores.

An alternate way to load jars is with the <lib> directive in 
solrconfig.xml ... but I don't recommend that approach.

Thanks,
Shawn

Reply via email to