docs(solr): document configuration.modules for solr 9.9+#5563
Draft
dephekt wants to merge 2 commits into
Draft
Conversation
Solr 9.8 made <lib> directives in solrconfig.xml opt-in (need -Dsolr.config.lib.enabled=true), and 10.0 (SOLR-16781) removed the handling code entirely. The replacement on 9.8+ is the SOLR_MODULES environment variable, which the Solr service agent now renders from a new customer-controlled configuration.modules field on the 9.9 and 10.0 manifests. Document the new field on both the Platform.sh and Upsun Solr service pages so customers upgrading from 9.6 (most notably Drupal + search_api_solr users, who rely on bundled modules like extraction and analysis-extras) know exactly what to add to services.yaml. Pre-9.9 versions are unaffected and continue to load modules from <lib> directives, so customers staying on 9.6 do not need to change anything. The new section sits between "Default configuration" and "Limitations" under "Solr 6 and later" rather than rewriting the existing "Available plugins" table, which describes the unconditional JTS and ICU4J classpath additions handled by the agent's post-install hook (a separate concern from the bundled-modules opt-in story). Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
|
Your Upsun Fixed environment has successfully deployed. 🚀 See the changed pages: Upsun Fixed docs |
Member
Author
|
Just following up if this is ready to be merged? Or if you need any info from me. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Solr 9.8 made directives in solrconfig.xml opt-in (need
-Dsolr.config.lib.enabled=true), and 10.0 (SOLR-16781) removed the handling code entirely. The replacement on 9.8+ is theSOLR_MODULESenvironment variable (docs), which the Solr service agent now renders from a new customer-controlled configuration.modules field on the 9.9 and 10.0 manifests.Document the new field on both the Platform.sh and Upsun Solr service pages so customers upgrading from 9.6 (most notably Drupal + search_api_solr users, who rely on bundled modules like extraction and analysis-extras) know exactly what to add to services.yaml. Pre-9.9 versions are unaffected and continue to load modules from directives, so customers staying on 9.6 do not need to change anything.
The new section sits between "Default configuration" and "Limitations" under "Solr 6 and later" rather than rewriting the existing "Available plugins" table, which describes the unconditional JTS and ICU4J classpath additions handled by the agent's post-install hook (a separate concern from the bundled-modules opt-in story).