Select a category on the left, to get your answers quickly
To setup your Drupal instance with Opensolr, you can either use the Search API Opensolr module, or, you can use Search API Solr.
In both cases, the setup should be pretty straight forward.
In the first case, you also have the option for AutoConfiguration, where you won't have to worry about the Solr server setup, at all.
All you'd have to do, is to create your index and start indexing your data.
The very important steps, however, if not using the Search API Opensolr module, are as follows:
Drupal - Search API Opensolr Opensolr, is Drupal-Ready with, the Search API Opensolr Module. Extends the main Search API Solr module and provides functionality for connecting and managing Solr using the Opensolr services. Download Now |
Some issues to be mindful about.
Drupal, has changed the way it works, and now, for path, it only requires you to have a SLASH.
Basically, what we call Path (/solr/index_name), in Opensolr, it should be / for your Drupal setup.
And what Drupal calls SolrCore, should be the Name of your Opensolr Index.
Also, if you use Opensolr in SolrCloud mode, please note that the solr server path is /solrcloud instead of /solr. (i.e.: https://server.opensolr.com/solrcloud/index_name/select?...)
So, unless Drupal has decided to hard-code the /solr part of the connection URL, you should be able to use your Opensolr SolrCloud Index, and set your path, in Drupal as /solrcloud, instead of / (slash).
Ultimately, we will help you upload your config files, regardless of the Solr Version you decide to use, as usual, we'll do this for free, and, instantly, during our office hours.
You might also want to watch the clip about all external integration issues.
It is a common misconception, that, if your Drupal module, or any other Solr plugin, requires, say, Solr Version 6.4.x, and Opensolr only provides Solr version 6.1.x, you can't use it with Opensolr.
With small modifications to your Solr config files, we can make your config files work on any of our Solr versions, without any impact on your Solr integration, or functionality overall.
Of course, migrating from one major Solr Version to another, isn't that straight forward, but, we can even, do that.
However, I can't stress enough that, migration between any Solr minor Versions is not only possible, it's even recommended, since we'll do it all for you, if you want to save time, and money, since, of course, Opensolr also offers FREE membership now.
It has also been a common misconception, that, your Opensolr connection URL returns 404 NOT FOUND, and therefore, it can not be used, and something must be broken.
In your Opensolr Control Panel, you will see your connection url as something like the following:
https://useast612.solrcluster.com/solr/opensolr/
Now, that URL, will always return an HTTP STATUS 404 NOT FOUND.
Ironically, that means everything is OK.
Your application will use that, as a base connection URL, and append other Solr Request Handlers to it, as you can see in this example:
https://useast612.solrcluster.com/solr/opensolr/select?q=*:*&wt=json&indent=true&start=0&rows=50&fl=title,description&fq=+content_type_text:(html)
We have added the /select Request Handler, and that very same connection URL is now responding with a full Solr json format response.
It's an OpenSolr Miracle!
Here are a few things to check if your Drupal won't connect to your Opensolr Index/Cluster.
1. Make sure you are using the latest Search API Opensolr module from the Drupal community, if you are using Drupal 8+ as this will make things much easier for you.
2. In your Drupal Solr Server settings, please select Solr with Basic AUTH OR Opensolr With Basic Auth
3. DO NOT forget to set the Opensolr Index AUTH Credentials, in your Drupal Solr Server Settings page, as it is described here
4. Try to set a shorter password for your Opensolr Index by going to your Index Security Tab in your Opensolr Index Control Panel (See image below). Replace INDEX_NAME with your own index name. (https://opensolr.com/admin/solr_manager/tools/INDEX_NAME#security)
Then try to use the new credentials in your Drupal Settings Page.
5. Make sure you upload the Solr configuration Files, provided by Drupal, in your Opensolr Index Control Panel, at: https://opensolr.com/admin/solr_manager/tools/INDEX_NAME#configuration (Replace INDEX_NAME with your own index name)
6. Make sure you use the correct connection parameters as indicated in the Opensolr Index Control Panel Dashboard: https://opensolr.com/admin/solr_manager/tools/INDEX_NAME#overview (Replace INDEX_NAME with your own index name)
In this clip we will talk about some of the most common drupal configuration issues, based on the solr configuration files provided by the Drupal search api module.
Error is:
SOLUTION:
(replace INDEX_NAME with your own Opensolr INDEX NAME)
That's all because you are using updateLog in your solrconfig.xml
Also, if you go here:
Drupal 6.x Known issue:
Looking at solrconfig_extra.xml you will find stuff like this:
<str name="accuracy">0.5</str>
<str name="maxEdits">2</str>
<str name="minPrefix">1</str>
<str name="maxInspections">5</str>
<str name="minQueryLength">4</str>
<str name="maxQueryFrequency">0.01</str>
<str name="thresholdTokenFrequency">.01</str>
You will have to change it to stuff like this:
<int name="maxEdits">2</int>
<int name="minPrefix">1</int>
<int name="maxInspections">5</int>
<int name="minQueryLength">4</int>
<float name="maxQueryFrequency">0.01</float>
<float name="thresholdTokenFrequency">.01</float>
I hope it's obvious why...
And please try to find more occurrences of integers and floats being defined as strings, in the drupal config files... I'm sure there must be more erors like these, in other configs for other solr versions as well in drupal.