Clarify usage of the "solr path" setting in implementation details #3261
Conversation
This file contains 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
The default "Solr path" value from Search API Solr is incorrect, it defaults to "/solr", which doesn't work, it has to be just "/".
This can be an issue when changing from one Solr system to another, e.g. upgrading from v3 to v7 and from Drupal's Search API Solr module v1 to v4.
Noted the correct "Solr path" setting to use
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
The Problem/Issue/Bug:
Different systems use Solr API v1 and others use v2.
How this PR Solves The Problem:
Noted that the "Solr path" setting must be set to "/solr" when using Solr API v1 and just "/" when using Solr API v2.
Manual Testing Instructions:
Automated Testing Overview:
Related Issue Link(s):
https://drupal.slack.com/archives/C5TQRQZRR/p1632433128297900
Release/Deployment notes: