Magnolia 6.1 reached end of life on March 31, 2021. This branch is no longer supported, see End-of-life policy.
This page gives an overview of Magnolia's Solr-based search functionality and contains the release notes for the Solr module.
Please note that by default Magnolia's search functionality is provided by Jackrabbit's search functionality (see Jackrabbit search). Use Solr if you need more advanced search options and especially if you need to manage assets in high volumes (100,000+ DAM assets)
Apache Solr is a standalone enterprise search server with a REST-like API: The documents are sent in for indexing via JSON, XML, CSV or binary over HTTP. The search queries are sent via HTTP GET and the results are received in JSON, XML, CSV or binary form.
Apache Solr uses the Lucene library and is:
- Scalable – Solr scales by distributing work (indexing and query processing) to multiple servers in a cluster.
- Ready to deploy – Solr is open source, is easy to install and configure, and provides a preconfigured example to help you get started.
- Optimized for search – Solr is fast and can execute complex queries in subsecond speed, often only tens of milliseconds.
- Large volumes of documents – Solr is designed to deal with indexes containing many millions of documents.
- Text-centric – Solr is optimized for searching natural-language text, like emails, web pages, resumes, PDF documents, and social messages such as tweets or blogs.
(from Chapter 1 of Solr in Action)
Magnolia's Solr-based search capability is provided by the Solr module (full name Magnolia Solr Search Provider module), which consists of the following three key submodules:
For installation, configuration information and Solr module release notes please see the Solr module page tree.
To create a custom sitemap with Solr in four easy steps, please refer to the page called Step-by-step integrating Solr in Magnolia and generating custom sitemap available on the Magnolia Community Wiki.