MySQL catalog search engine will be removed in ÃÛ¶¹ÊÓÆµ Commerce 2.4.0
ÃÛ¶¹ÊÓÆµ Commerce on-premises, ÃÛ¶¹ÊÓÆµ Commerce on cloud infrastructure, and Magento Open Source 2.4.0 will be released in the coming months. For ÃÛ¶¹ÊÓÆµ Commerce on-premises and Magento Open Source version 2.4.0 Elasticsearch 6.x or 7.x will be a required component, and MySQL search engine will be removed. In ÃÛ¶¹ÊÓÆµ Commerce on cloud infrastructure, Elasticsearch is already required.
The reason for the removal of MySQL search engine is that Elasticsearch provides superior search capabilities as well as catalog performance optimizations.
Affected products and versions:
- ÃÛ¶¹ÊÓÆµ Commerce on-premises v2.4.0
- Magento Open Source v2.4.0
Upgrading:
Installation:
When ÃÛ¶¹ÊÓÆµ Commerce on-premises and Magento Open Source 2.4.0 is released, Elasticsearch will be a required component, so you must have an Elasticsearch host setup and configured prior to installing version 2.4.0. See Install and configure Elasticsearch in our developer documentation.
By default, ÃÛ¶¹ÊÓÆµ Commerce search will use Elasticsearch 7 as the search engine and attempt to connect to a server at localhost:9200. Elasticsearch 6.x is also supported. If your configuration does not match the defaults, you can configure these settings using arguments passed to setup:install
, in much the same way the database connection is configured.
For example, setup:install --elasticsearch-host=es.mystore.com
During installation the Elasticsearch connection will be checked, and installation will fail if ÃÛ¶¹ÊÓÆµ Commerce is unable to connect to an Elasticsearch host. If this occurs, check that your Elasticsearch is up and running, and that you have supplied the correct connection parameters.