- Issue created by @das-peter
- π¨πSwitzerland das-peter
If I'm not completely mistaken
-Dsolr.config.lib.enabled=true
would have to be set via environment variables / startup parameters.
E.g. something like this
SOLR_OPTS="$SOLR_OPTS -Dsolr.config.lib.enabled=true"
However, the only location in the jump start template that would allow that is docker-compose.yml
And there we might as well switch to use the env varSOLR_MODULES
:
SOLR_MODULES="extraction,langid,ltr,analysis-extras"
- π¨πSwitzerland das-peter
Created a PR with a possible approach how to tackle this.
Related PR: https://github.com/mkalkbrenner/search_api_solr/pull/105
Patch: https://github.com/mkalkbrenner/search_api_solr/pull/105.patch & as attachmentI'm not sure if we the module can or should provide further assistance with fixing the breaking change.
It hit me off guard when our solr image was re-built and it took me quite a while to dig through everything to sort out what had gone wrong.
I wonder if there's a way to check the available modules / the set config via API and show a clear message in the Search API Overview if this is off. - π©πͺGermany mkalkbrenner π©πͺ
Within the Solarium library tests, we also went for
SOLR_MODULES=extraction
-
das-peter β
authored 21497745 on 4.x
Issue #3508084: Breaking change in Solr 9.8: solr.config.lib.enabled (#...
-
das-peter β
authored 21497745 on 4.x
Automatically closed - issue fixed for 2 weeks with no activity.