Solr Search Engine Bundle is bundled by default in eZ Platform and these instructions are for configuring it, for eZ Publish Platform 5.4 instructions see Solr Search Engine Bundle. |
Version 1.0.x of Solr Bundle primarily aims to be used as replacement for Legacy (SQL-based) search engine for better scalability and performance (especially with field criteria and sort clauses). And while it also provides better full text search thanks to Solr, more advance search features like Faceting will come in later releases. |
ezplatform-solr-search-engine as the package is called, aims to be a transparent drop in replacement for the SQL based "Legacy" search engine powering Search API by default. By enabling Solr and re-indexing your content, all your exising Search queries using SearchService, will be powered by Solr automatically. This allows you to scale up your eZ Platform installation and be able to continue development locally against SQL engine, and have test infrastructure, Staging and Prod powered by Solr. Thus remove considerable load from your database so it can focus on more important things, like publishing 
.
Se Architecture page for further information on the architecture of eZ Platform.
This step is not needed for eZ Platform as of 15.09, however it is kept here for reference in case you have previously disabled the bundle. |
Add/Update composer dependencies:
composer require --no-update ezsystems/ezplatform-solr-search-engine:~1.0 composer update |
app/AppKernel.php file: new EzSystems\EzPlatformSolrSearchEngineBundle\EzSystemsEzPlatformSolrSearchEngineBundle()
| Example here is for single core, look to Solr documentation for configuring Solr in other ways, also see the provided configuration for some examples. |
First, download and extract Solr, we currently support Solr 4.10.4:
Secondly, copy configuration files needed for eZ Solr Search Engine bundle, here from the root of your project to the place you extracted Solr:
# Make sure to change the /opt/solr/ path with where you have placed Solr cp -R vendor/ezsystems/ezplatform-solr-search-engine/lib/Resources/config/solr/* /opt/solr/example/solr/collection1/conf/ /opt/solr/bin/solr start -f |
Thirdly, Solr Bundle does not commit solr index changes directly on repository updates, leaving it up to you to tune this using solrconfig.xml as best practice suggests, example config:
<autoCommit>
<!-- autoCommit is here left as-is like it is out of the box in Solr 4.10.4, this controls hard commits for durability/replication -->
<maxTime>${solr.autoCommit.maxTime:15000}</maxTime>
<openSearcher>false</openSearcher>
</autoCommit>
<autoSoftCommit>
<!-- Soft commits controls mainly when changes becomes visible, by default we change value from -1 (disabled) to 100ms, to try to strike a balance between Solr performance and staleness of HttpCache generated by Solr queries -->
<maxTime>${solr.autoSoftCommit.maxTime:100}</maxTime>
</autoSoftCommit> |
The Solr search engine bundle can be configured many ways, here are some examples:
Out of the box in eZ Platform the following is enabled for simple setup:
ez_search_engine_solr:
endpoints:
endpoint0:
dsn: %solr_dsn%
core: collection1
connections:
default:
entry_endpoints:
- endpoint0
mapping:
default: endpoint0 |
In the following example we have decided to separate one language as the installation contains several similar languages, and one very different language that should be receive proper language analysis for proper stemming and sorting behavior by Solr:
ez_search_engine_solr:
endpoints:
endpoint0:
dsn: %solr_dsn%
core: core0
endpoint1:
dsn: %solr_dsn%
core: core1
connections:
default:
entry_endpoints:
- endpoint0
- endpoint1
mapping:
translations:
- jpn-JP: endpoint1
# Other languages, for instance eng-US and other western languages are sharing core
default: endpoint0 |
If full language analysis features are preferred, then each language can be configured to separate cores.
Note: Please make sure to test this setup against single core as it might perform worse then single core if your project uses a lot for language fallbacks per siteaccess as queries will then be performed across several cores at once.
ez_search_engine_solr:
endpoints:
endpoint0:
dsn: %solr_dsn%
core: core0
endpoint1:
dsn: %solr_dsn%
core: core1
endpoint2:
dsn: %solr_dsn%
core: core2
endpoint3:
dsn: %solr_dsn%
core: core3
endpoint4:
dsn: %solr_dsn%
core: core4
endpoint5:
dsn: %solr_dsn%
core: core5
endpoint6:
dsn: %solr_dsn%
core: core6
connections:
default:
entry_endpoints:
- endpoint0
- endpoint1
- endpoint2
- endpoint3
- endpoint4
- endpoint5
- endpoint6
mapping:
translations:
- jpn-JP: endpoint1
- eng-US: endpoint2
- fre-FR: endpoint3
- ger-DE: endpoint4
- esp-ES: endpoint5
# Not really used, but specified here for fallback if more languages are suddenly added by content admins
default: endpoint0
# Also use separate core for main languages (differs from content object to content object)
# This is useful to reduce number of cores queried for always available language fallbacks
main_translations: endpoint6 |
The following is an example of configuring Solr Search Engine, where connection name is same as in example above, and engine is set to solr:
ezpublish:
repositories:
main:
storage:
engine: legacy
connection: default # This should be the connection you had from before for repository
search:
engine: solr # One of legacy (default) or solr
connection: default # If legacy same as storage applies, if solr use same as you defined in step 3 |
Some exceptions might happen on indexing if you have not configured your setup correctly, here are the most common issues you may encounter:
|
Last step is to execute initial indexation of data:
php app/console --env=prod --siteaccess=<name> ezplatform:solr_create_index |
After completing the installation you are now free to use your site as usual. If you get any exceptions for missing features, have feedback on performance, or want to discuss, join our community slack channel at https://ezcommunity.slack.com/messages/ezplatform-use/