Indexing eContent data¶
If Ibexa Commerce is configured to use eContent as data provider, the following things have to be taken into consideration when indexing.
eContent data can be indexed by executing the following command:
eContent Solr configuration uses two cores to keep search services available while indexing. This means that the indexer indexes eContent data in a back core, and then the indexer can be executed again with a swap parameter to swap the cores.
||Indexes directly on the live core (and not on the back core).If you use
||Does not index, but swaps the cores instead.|
||Specifies the languages to index.|
||Enables or disables Solr spellcheck (aka "Did you mean?" functionality)|
||Solr string fields are lowercased, therefore this configuration is used to specify an additional Solr
Custom indexing using plugins¶
eContent indexer also supports a plugin architecture for adding additional logic to the indexing process.
The plugin can index price ranges. Given a product price, it creates a range index based on that price. For example, for the price of $150, the output can be 100-200.
In order to work the plugins must implement the
For more information, see Custom indexer plugin for eContent