I have a Solr server running on a URL like http://www.example.com:XXXXXX@solr.example.com:8080/solr-drupal/www.exam... where solr.example.com is my Solr instance, www.example.com is my domain name and XXXXX is the password. The plan is to set up one solr server for multiple sites, hence the above more complicated url. This works perfectly with the ApacheSolr module but everything fails when I attempt to use the above settings with xc_solr - it is unable to ping or connect to the solr instance.
The attached patch borrows heavily from the apachesolr module but it does now allow me to use the xc_solr module for harvested records. It probably needs some tweaking, though I'm beginning to think that maybe the correct solution would be to create a dependency on the ApacheSolr module itself?
| Comment | File | Size | Author |
|---|---|---|---|
| #3 | 1014786.patch | 13.88 KB | stella |
| #1 | xc_solr_failed_connection.patch | 13.2 KB | stella |
| xc_solr_failed_connection.patch | 13.11 KB | stella |
Comments
Comment #1
stella commentedErrr here's the correct patch, this time created from the correct directory.
Comment #2
pkiraly commentedThanks for the patch. I'd like to ask more time to evaluate and thinking about your solution, whether it is fit for different use cases.
Comment #3
stella commentedNo problem. Here's an updated patch - I missed one instance of Apache_Solr_ServiceXc in previous patch, which should have been Drupal_Apache_Solr_ServiceXc. I still think that the xc_solr module should extend apachesolr module though (and external libraries shouldn't be modified or added to drupal.org's CVS by the way).
Comment #4
stella commentedThis doesn't appear to be an issue with the latest dev version.
Comment #5
stella commentederrr my bad, it's still an issue, sorry.