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.
I did some co-working today with @stovak and @jazzsequence trying to work out #181. We found that some requests from Drupal to Solr included the name of the core in the path of the request and some did not. (We did this by toggling
debug
property here: https://github.com/pantheon-systems/search_api_pantheon/blob/8.x/src/Services/PantheonGuzzle.php#L63)Those that did not were 404s, those that did were 200s. So here's a hacky re-insertion of the core name that at least gets rid of the error in #181.
Someone with a better understanding of Solr than me could do more to explain. If I kept going, I'd stop comparing search_api_pantheon on a Pantheon multidev to search_api_pantheon on DDev and instead do a DDev to DDev comparison. I bet DDev works fine with regular search_api_solr.