The Solr Workbench submodule of the Magnolia
Solr module provides a
Magnolia Solr container that can be used instead of the JCR container
for list, search and thumbnail views in a content app. This page
describes how to configure the submodule to use Solr’s functionality in
the 5 UI Assets app and for indexing of the assets it manages.
Magnolia uses the following search containers that backup the search
view in the UI:
info.magnolia.ui.workbench.search.SearchJcrContainer for Jackrabbit.
info.magnolia.search.solrsearchprovider.workbench.SolrContainer for
Solr.
In general, you can use these containers in any JCR based
Content
App. Similarly, indexing is workspace-based and hence one workspace may
use Jackrabbit’s indexing functionality, another one Solr’s indexing
functionality.
You can also define and use your own custom container, especially in
case you need to use both Jackrabbit and Solr together in one workspace.
Creating a dedicated core for the Assets app
When Apache Solr is running, create a new core called dam_wokbench for the
Assets app:
The Solr Workbench module introduces
info.magnolia.search.solrsearchprovider.workbench.SolrJcrContentConnectorDefinition. It allows you to specify which
client
should be used.
The configuration snippet below is a YAML decoration showing how to use
SolrJcrContentConnectorDefinition in the app:
The submodule provides presenter and definition classes for list, search
and thumbnail views. The configuration decoration snippet below shows SOLR-based
content view definitions for the list, thumbnail and search views in the
DAM app’s browser: