Respect the submission guidelines above! Drupal.org issue forks cause additional work for the project maintainer!

Setup

  • Solr version: 7.7.3
  • Drupal Core version: 7.8.4
  • Search API version: 7.x-1.28
  • Search API Solr version: 7.x-1.15
  • Configured Solr Connector:

Issue

With the current security issue with SOLR 7 not being corrected and a move to SOLR 8 being required, provide an upgrade path for Drupal 7 to support SOLR 8.

Comments

ElusiveMind created an issue. See original summary.

mkalkbrenner’s picture

I'm not the maintainer of the Drupal 7 module version. But I think that drunken monkey will not find time to work on this larger task.
If you want to use Solr 8, consider a migration to Drupal 9.
Meanwhile you should secure your Solr 7 installation like described at https://solr.apache.org/security.html
As Solr 7.7 is still supported, I think we'll see a security release.

mkalkbrenner’s picture

Category: Feature request » Support request
Status: Active » Fixed

If you want to stay with Drupal 7 you need to apply the Solr hardening manually according to Solr's documentation:
https://solr.apache.org/security.html#apache-solr-affected-by-apache-log...

Status: Fixed » Closed (fixed)

Automatically closed - issue fixed for 2 weeks with no activity.

johnrosswvsu’s picture

We may need to revisit this since some site are still using Drupal 7. We were able to make this module work with SOLR 8.

Setup

  • Solr version: 8.11.x
  • Drupal Core version: 7.103
  • Search API version: 7.x-1.29
  • Search API Solr version: 7.x-1.16

Plus this patch.

greg.1.anderson’s picture

This has been tested on Pantheon and found to be working. I would set to RTBC, but only maintainers can re-open issues.

drunken monkey’s picture

Status: Closed (fixed) » Needs review

Thanks, I’ll take a look.

mkalkbrenner’s picture

For sure you can commit that patch in the Drupal 7 branch. But the 7.x module is already marked as unsupported, just like Drupal 7 itself.

BTW it is a bit strange that people want to update to newer Solr versions but not to newer Drupal versions ;-)

  • drunken monkey committed 44d5d736 on 7.x-1.x
    Issue #3254212 by johnrosswvsu, drunken monkey: Added support for Solr 8...
drunken monkey’s picture

Status: Needs review » Fixed

I agree, people should definitely get off those old Drupal versions. And yes, I won’t provide support for those anymore.
But, as said on Slack, just commiting patches as-is (or fixing one typo, admittedly) should still be fine.
Committed. Thanks again!

elusivemind’s picture

Thank you for supporting this. It will also help those of us working on LTS Drupal 7 or alternatives such as BackdropCMS - so it is a noble effort. I appreciate it.

greg.1.anderson’s picture

Thanks so much! Could you roll a new release for search_api_solr 7.x-1.x to include this addition, when you have a chance?

Status: Fixed » Closed (fixed)

Automatically closed - issue fixed for 2 weeks with no activity.

narkoff’s picture

@greg.1.anderson did you get this patch working on Pantheon Solr servers (Pantheon seems to restrict D7 sites on Solr 8), or on Pantheon hosted D7 site using Solr on other service like OpenSolr, WebSolr, etc?

jonhattan’s picture

FTR, the patch committed ships with this config:

# schema.xml
<luceneMatchVersion>${solr.luceneMatchVersion:LUCENE_60}</luceneMatchVersion>

# solrcore.properties
solr.luceneMatchVersion=6.0

You want to remove the line from solrcore.properties and update the other one to LUCENE_80.