Magnolia 6.0 reached end of life on June 26, 2019. This branch is no longer supported, see End-of-life policy.
The latest version of the Solr module is 6.1.4.
Solr module compatibility with Apache Solr
This version contains changes in
managed-schema. Please read the notes below before updating.
magnolia-solr-workbench. It provides a SolrContainer for list, search and thumbnail views in the content apps.
<field name="jcrname" type="string" stored="true" indexed="true"/>).
<field name="nodetype" type="string" stored="true" indexed="true"/>).
<dynamicField name="asset_*" type="text_general" indexed="true" stored="true" multiValued="false"/>).
<copyField source="*" dest="_text_"/>(replaced by
solrconfig.xml, see also below).
*_point(in collision with the
*_pointfields when parsed by Apache Tika in documents).
*_id (Indonesian)(in collision with the
*_idfields when parsed by Apache Tika in documents).
CloneFieldUpdateProcessorFactorywas added into the
add-unknown-fields-to-the-schemaupdate request processor chain. This replaces
<copyField source="*" dest="_text_"/>, which was removed from the
ignored_*fields are by default excluded from copying to the
To update to version 5.2, refer to the Installing Apache Solr page. After a successful installation of Solr 7, retrigger the indexers (
/modules/content-indexer/config/indexers/<indexer_name>) by changing their property indexed to
This version contains changes in
managed-schema please read the notes before update to 5.0.2.
Fixed na issue of two indexers/crawlers mutually overwriting the resulting index when indexing the same content. For example when one indexer was for indexing the English translation and other one for indexing the German translation. - MGNLEESOLR-102Getting issue details... STATUS
Problem was caused by using jcr uuid(indexers) and url(crawlers) as unique identifier for solr indexes. To fix this issue changes in
managed-schema were required.
managed-schemawas changed to
solrconfig.xmlnow generates the
uuidfield from a combination of
idfields. The deduplication method is used to generate the uuid. For more details see the change in code diff.
If you don't plan to index same content by two different indexers or crawlers then you don't need to update your
managed-schema for your solr core. Only change what you need to do is add
uniqueKeyField property with value
id into your solr sear result page.
Use new managed-schema and solrconfig.xml configuration files for your solr core and for
It's needed to recreate all Solr indexes, because of the changes in configuration files. Probably the easiest way to do it is recreate the solr core and then retrigger indexing in Magnolia.
managed-schemaconfiguration files for
$SOLR_HOME/server/solr/configsets/magnolia_data_driven_schema_configMagnolia config set.
magnolia core an create it again
cd $SOLR_HOME/bin ./solr delete -c magnolia ./solr create_core -c magnolia -d magnolia_data_driven_schema_configs
Retrigger the indexers, by changing their property
Solr Search Provider module version 5.0 brings support to Solr 5 (officially tested with version 5.3.1).
Full changelog for version 5.0 https://jira.magnolia-cms.com/browse/MGNLEESOLR/fixforversion/18141
Regarding the changes in the module it's recommended completely recreate the Solr indexes after to upgrade to version 5.0.
org.apache.solr.client.solrj.SolrServer is deprecated and was replaced by org.apache.solr.client.solrj.SolrClient in solr-solrj 5.x library. Because of that info.magnolia.search.solrsearchprovider.MagnoliaSolrBridge#getSolrServer method was changed to info.magnolia.search.solrsearchprovider.MagnoliaSolrBridge#getSolrClient method.
Solr Search Provider module version 3.0 delivers the following key fixes and enhancements:
magnolia-solr-search-provider-theme module has gone - MGNLEESOLR-66Getting issue details... STATUS
Full changelog for version 3.0 https://jira.magnolia-cms.com/browse/MGNLEESOLR/fixforversion/17434
Regarding the changes in the module it's recommended completely recreate the Solr indexes after to upgrade to version 3.0.