Last updated 24 January 2015. Created on 20 May 2013.
Edited by drunken monkey. Log in to edit this page.

This section documents all settings that are available when creating/editing a Search API server with the "Solr search" service class.

HTTP protocol, Solr host, Solr port, Solr path

These are just used to specify the URL to the Solr server. If you're not sure how to break a URL down into these parts, see this Wikipedia article. The URL (specifically the path) you should enter is the top-most one leading to the Solr server. In Solr 4, this is the one which shows the admin interface (without the # and everything following it). In Solr 3 or below, the one which shows the welcome screen, and which shows the admin interface if you append "/admin".

It doesn't matter whether to include the leading or trailing slashes ("/") in the path, these will be added automatically by the service class.

Basic HTTP authentication

If your Solr server is protected by basic HTTP authentication, enter the username and password here.

Advanced » Return an excerpt for all results

When this option is enabled and a search with keywords is executed on the server, search excerpts will be created by Solr for all results. You can then use these, e.g., with the "Search: Excerpt" field in search views. Search pages will use the excerpts automatically if "Themed as search results" is selected as the view mode.

Advanced » Retrieve result data from Solr

This option allows you to retrieve the result data (the fields of the result items) directly from Solr instead of loading it from the database. This might have advantages regarding performance (though benchmarks indicate this isn't usually the case) or security (as access checks will always be made against the data that will also be shown).

However, due to technical restrictions this won't work for functionality which needs the complete entity to work. This includes showing Field API fields in Views, rendering an entity in a certain view mode (with Views or Pages), linking a displayed field in Views to its entity (you can use a custom link rewrite with the item ID to circumvent this) or using the "Additional access checks on result entities" option in Views.

Advanced » Highlight retrieved data

This option is only available if “Retrieve result data from Solr” is enabled. If this option is also enabled, occurrences of search keywords will be marked in the returned data.

Advanced » HTTP method

This setting determines the HTTP method used for sending search queries to the Solr server. See #1276970: Large queries break solr search for reasons to use POST instead of GET. In summary, if your searches might create large queries (with lots of filters, for example), using GET might lead to Solr errors during searches. However, if there's no chance of this happening, GET might be the better choice, as explained in #1997702: Using POST for all select queries.

Advanced » Autocomplete

These additional settings are only available if the Search API Autocomplete is enabled. They control which methods will be used to determine the autocompletion suggestions for indexes on this server.

Looking for support? Visit the forums, or join #drupal-support in IRC.