Closed (fixed)
Project:
Search API Solr
Version:
4.x-dev
Component:
Solr Configuration Generator
Priority:
Normal
Category:
Task
Assigned:
Unassigned
Issue tags:
Reporter:
Created:
6 Mar 2026 at 10:06 UTC
Updated:
11 Jun 2026 at 13:49 UTC
Jump to comment: Most recent, Most recent file
Comments
Comment #2
znerol commentedAfter copying over the 9.x templates, the
LUCENE_90value insolrconfig.xmlneeds to be adapted. According to lucene TestVersion.java it looks like the correct value isLUCENE_10_0.Comment #3
znerol commentedPR: https://github.com/mkalkbrenner/search_api_solr/pull/116
Comment #4
znerol commentedUp until Solr 9, it was necessary to use the
-cor--cloudflag to start solr in cloud mode. In Solr 10 this is now the default.Comment #5
znerol commentedThe
bin/postscript has been replaced with thebin/solr postcommand.Comment #6
znerol commentedThe deprecated
solrcore.propertiesconfiguration method has been removed. The ability to configure a core via a custom properties file using thecore.proprtiespropertiessetting remains.Comment #7
znerol commentedVery funny problem due to the size of the XML configuration:
This is because solr 10 docker image is based on a newer JDK image. And they thightened the limits in between.
Comment #8
znerol commentedExternalFileFieldfield type has been removed.Comment #9
znerol commentedThe alternative dutch stemmer which was selected using the
language="Kp"attribute is now the default stemming implementation.Comment #10
znerol commentedThe legacy Circuit Breaker named
CircuitBreakerManageris removed.Comment #12
znerol commentedI'm unable to get the github actions to work. It seems that
docker compose up -dinjump-start/solr10is failing to create thedrupalcollection. However, I cannot reproduce that locally. It always succeeds on my machine.Comment #13
znerol commentedComment #15
znerol commentedComment #16
znerol commentedComment #17
znerol commentedComment #18
znerol commentedComment #19
mkalkbrennerThanks for the MR. But the workflow must be different.
Instead of providing a jump-start config-set, a set of 10.x templates must be added to https://git.drupalcode.org/project/search_api_solr/-/tree/4.x/solr-conf-...
The tests should then automatically create a jump-start config-set from the templates. (I changed the gitlab CI config to pick up these newly generated jump-starts.)
This is important as this is the process running when users generate custom configs.
Furthermore, some code changes are required to allow a Solr 10.x config-set generation.
But the most important thing that is starnge is that the jump-start tests should have failed because there are no Solr 10.x templates.
Comment #20
znerol commentedThe solr templates are there, and also the changes in
SolrConfigSetController.phpandSolrConnectorPluginBase.php. But it looks like gitlab doesn't manage to render it...Comment #21
znerol commentedGuess the problem is this:
Comment #23
znerol commentedI've added a draft merge request without the changes in
jump-start.Comment #24
znerol commentedComment #25
znerol commentedRunning this in pre-production. There are no stats due to removal of mbean handler, but other than that things look good.
Comment #26
mkalkbrennerComment #31
idebr commented@mkalkbrenner can you tag a new release, so the option to run Solr 10 becomes available without using a dev release?