You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@solr.apache.org by "Flowerday, Matthew J" <ma...@gb.unisys.com.INVALID> on 2022/05/24 09:37:56 UTC
Issues trying to create a core under 9.0.0 (testing out product under the new version of Solr)
Hi There
I am trying to test Solr 9.0.0 on our product which is currently using
8.11.1. I have added our adjustments to the 9.0.0 versions of schema.xml and
solrconfig.xml and Solr starts up fine and I can access the Admin Tool
successfully.
When I try create a new core I get this error:
C:\solr-9.0.0\bin>solr create_core -c holmes
WARNING: Using _default configset with data driven schema functionality. NOT
RECOMMENDED for production use.
To turn off: bin\solr config -c holmes -p 9007 -action
set-user-property -property update.autoCreateFields -value false
ERROR: Parse error : <html>
<head>
<meta http-equiv="Content-Type" content="text/html;charset=ISO-8859-1"/>
<title>Error 500 java.lang.NoClassDefFoundError:
org/apache/lucene/analysis/util/TokenizerFactory</title>
</head>
<body><h2>HTTP ERROR 500 java.lang.NoClassDefFoundError:
org/apache/lucene/analysis/util/TokenizerFactory</h2>
<table>
<tr><th>URI:</th><td>/solr/admin/cores</td></tr>
<tr><th>STATUS:</th><td>500</td></tr>
<tr><th>MESSAGE:</th><td>java.lang.NoClassDefFoundError:
org/apache/lucene/analysis/util/TokenizerFactory</td></tr>
<tr><th>SERVLET:</th><td>default</td></tr>
<tr><th>CAUSED BY:</th><td>java.lang.NoClassDefFoundError:
org/apache/lucene/analysis/util/TokenizerFactory</td></tr>
<tr><th>CAUSED BY:</th><td>java.lang.ClassNotFoundException:
org.apache.lucene.analysis.util.TokenizerFactory</td></tr>
</table>
<h3>Caused by:</h3><pre>java.lang.NoClassDefFoundError:
org/apache/lucene/analysis/util/TokenizerFactory
It looks like it is having issues tracking down libraries. In the
solrconfig.xml I have set up the standard lib dir in the 9.0.0 version
<lib dir="${solr.install.dir:../../../..}/modules/ltr/lib"
regex=".*\.jar" />
In 8.11.1 we used
<lib dir="${solr.install.dir:../../../..}/dist/"
regex="solr-ltr-\d.*\.jar" />
Which was the 8.11.1 standard entry.
I am also worried that it looks like it using the _default configset. I have
set up a folder 'holmes' containing the structures within the
server\solr\configsets folder. Do I need to explicitly identify the config
set somewhere in 9.0.0?
I have also noticed in the schema.xml fieldType entries such as
<tokenizer class="solr.StandardTokenizerFactory"/>
And
<filter class="solr.StopFilterFactory"
ignoreCase="true" words="stopwords.txt" />
Are now
<tokenizer name="standard"/>
And
<filter name="stop" ignoreCase="true"
words="stopwords.txt" />
Where 'name' instead of 'class' in now being used. We have set up a number
of our own field types - would we need to now set them up in the same way in
9.0.0? Could it be the classes we are using are failing to be found?
Many Thanks
Matthew
Matthew Flowerday | Consultant | ULEAF
Unisys | 01908 774830| <ma...@unisys.com>
matthew.flowerday@unisys.com
Address Enigma | Wavendon Business Park | Wavendon | Milton Keynes | MK17
8LX
<http://www.unisys.com/>
THIS COMMUNICATION MAY CONTAIN CONFIDENTIAL AND/OR OTHERWISE PROPRIETARY
MATERIAL and is for use only by the intended recipient. If you received this
in error, please contact the sender and delete the e-mail and its
attachments from all devices.
<http://www.linkedin.com/company/unisys> <http://twitter.com/unisyscorp>
<http://www.youtube.com/theunisyschannel>
<http://www.facebook.com/unisyscorp> <https://vimeo.com/unisys>
<http://blogs.unisys.com/>
RE: Issues trying to create a core under 9.0.0 (testing out product under the new version of Solr)
Posted by "Flowerday, Matthew J" <ma...@gb.unisys.com.INVALID>.
Hi There
I resolved the issues I was having. We have some custom tokenizers which
needed to have been compiled with Solr 9.0.0 libraries. Now all ok and have
re-indexed my test system without issue.
I also found that still referencing tokenizers and filters by class instead
of names (which the 9.0.0 schema does) still works.
Regards
Matthew
Matthew Flowerday | Consultant | ULEAF
Unisys | 01908 774830| <ma...@unisys.com>
matthew.flowerday@unisys.com
Address Enigma | Wavendon Business Park | Wavendon | Milton Keynes | MK17
8LX
<http://www.unisys.com/>
THIS COMMUNICATION MAY CONTAIN CONFIDENTIAL AND/OR OTHERWISE PROPRIETARY
MATERIAL and is for use only by the intended recipient. If you received this
in error, please contact the sender and delete the e-mail and its
attachments from all devices.
<http://www.linkedin.com/company/unisys> <http://twitter.com/unisyscorp>
<http://www.youtube.com/theunisyschannel>
<http://www.facebook.com/unisyscorp> <https://vimeo.com/unisys>
<http://blogs.unisys.com/>
From: Flowerday, Matthew J <>
Sent: 24 May 2022 10:38
To: users@solr.apache.org
Subject: Issues trying to create a core under 9.0.0 (testing out product
under the new version of Solr)
Hi There
I am trying to test Solr 9.0.0 on our product which is currently using
8.11.1. I have added our adjustments to the 9.0.0 versions of schema.xml and
solrconfig.xml and Solr starts up fine and I can access the Admin Tool
successfully.
When I try create a new core I get this error:
C:\solr-9.0.0\bin>solr create_core -c holmes
WARNING: Using _default configset with data driven schema functionality. NOT
RECOMMENDED for production use.
To turn off: bin\solr config -c holmes -p 9007 -action
set-user-property -property update.autoCreateFields -value false
ERROR: Parse error : <html>
<head>
<meta http-equiv="Content-Type" content="text/html;charset=ISO-8859-1"/>
<title>Error 500 java.lang.NoClassDefFoundError:
org/apache/lucene/analysis/util/TokenizerFactory</title>
</head>
<body><h2>HTTP ERROR 500 java.lang.NoClassDefFoundError:
org/apache/lucene/analysis/util/TokenizerFactory</h2>
<table>
<tr><th>URI:</th><td>/solr/admin/cores</td></tr>
<tr><th>STATUS:</th><td>500</td></tr>
<tr><th>MESSAGE:</th><td>java.lang.NoClassDefFoundError:
org/apache/lucene/analysis/util/TokenizerFactory</td></tr>
<tr><th>SERVLET:</th><td>default</td></tr>
<tr><th>CAUSED BY:</th><td>java.lang.NoClassDefFoundError:
org/apache/lucene/analysis/util/TokenizerFactory</td></tr>
<tr><th>CAUSED BY:</th><td>java.lang.ClassNotFoundException:
org.apache.lucene.analysis.util.TokenizerFactory</td></tr>
</table>
<h3>Caused by:</h3><pre>java.lang.NoClassDefFoundError:
org/apache/lucene/analysis/util/TokenizerFactory
It looks like it is having issues tracking down libraries. In the
solrconfig.xml I have set up the standard lib dir in the 9.0.0 version
<lib dir="${solr.install.dir:../../../..}/modules/ltr/lib"
regex=".*\.jar" />
In 8.11.1 we used
<lib dir="${solr.install.dir:../../../..}/dist/"
regex="solr-ltr-\d.*\.jar" />
Which was the 8.11.1 standard entry.
I am also worried that it looks like it using the _default configset. I have
set up a folder 'holmes' containing the structures within the
server\solr\configsets folder. Do I need to explicitly identify the config
set somewhere in 9.0.0?
I have also noticed in the schema.xml fieldType entries such as
<tokenizer class="solr.StandardTokenizerFactory"/>
And
<filter class="solr.StopFilterFactory"
ignoreCase="true" words="stopwords.txt" />
Are now
<tokenizer name="standard"/>
And
<filter name="stop" ignoreCase="true"
words="stopwords.txt" />
Where 'name' instead of 'class' in now being used. We have set up a number
of our own field types - would we need to now set them up in the same way in
9.0.0? Could it be the classes we are using are failing to be found?
Many Thanks
Matthew
Matthew Flowerday | Consultant | ULEAF
Unisys | 01908 774830| <ma...@unisys.com>
matthew.flowerday@unisys.com
Address Enigma | Wavendon Business Park | Wavendon | Milton Keynes | MK17
8LX
<http://www.unisys.com/>
THIS COMMUNICATION MAY CONTAIN CONFIDENTIAL AND/OR OTHERWISE PROPRIETARY
MATERIAL and is for use only by the intended recipient. If you received this
in error, please contact the sender and delete the e-mail and its
attachments from all devices.
<http://www.linkedin.com/company/unisys> <http://twitter.com/unisyscorp>
<http://www.youtube.com/theunisyschannel>
<http://www.facebook.com/unisyscorp> <https://vimeo.com/unisys>
<http://blogs.unisys.com/>