Search API Fusion
Security covered
This module integrates the Search API module with Lucidworks Fusion, a search platform based on Apache Solr. It routes search and autocomplete queries to Fusion's Query API, while other requests go to its Solr API. The integration supports features like autocompletion, spell checking, faceting, promoted results, and signals.
This module provides a Lucidworks Fusion backend for the Search API module.
All requests are routed to the Solr API except:
- Search and autocomplete queries which are routed to the Query API
- Signals are routed to the Signals API
Requirements
- Search API
- Search API Solr since Fusion is based on Apache Solr
- Sarnia (D7 only)
Features supported
- Autocompletion based on Query Pipelines (requires the module search_api_autocomplete)
- Spell checking (requires the module search_api_spellcheck)
- Faceting (requires the module facetapi in D7 and facets in D8+)
- Landing pages (promoted results)
- Request and Click Signals
Usage (D7)
- Enable the module and its requirements
- Go to
admin/config/search/search_apiand add a new server with service classSarnia Fusion service- Sarnia should automatically generate a read-only index under this server - You can now create a view or a page based on this index, using either the Search API View or Search API Page module
Usage (D8+)
- Enable the module and its requirements
- Go to
/admin/config/search/search_apiand add a new server with backendSolrand Solr connectorFusion; provide a Fusion app and search query profile - Create a search index based on the search server you just created ; if your Fusion index is populated via a Fusion index pipeline or some other process outside of Druapl then you may want to make it read-only
- You can now create a search view at
/admin/structure/views - For autocompletion: enable search_api_autocomplete, open the Search API Index you created and click on the
Autocompletetab and add a suggesterFusion query profile