MySQL catalog search engine will be removed in Magento 2.4.0 . You must have Elasticsearch host setup and configured prior to installing version 2.4.0. Refer to Install and configure Elasticsearch .
This article provides a patch for the known Magento Commerce (Cloud) 2.2.3 issue related to getting different search results for the same search query with MySQL and ElasticSearch.
Issue:
Your catalog search results with same filters set, differ depending on the search engine being used, MySQL or ElasticSearch.
Steps to reproduce :
- Install and configure ElasticSearch.
- On the storefront, select one of the filters.
- Make note of the number of matching products.
- Configure the default MySQL search .
- On the storefront, select one of the filters.
- Make note of the number of matching products.
Expected result :The number of matching products is the same.
Actual result :The number of matching products is different.
Patch
The patches are attached to this article. To download a patch, scroll down to the end of the article and click the required file name, or click one the following links:
Download MDVA-12312_EE_2.2.3_COMPOSER_v1.patch
Download MDVA-14172_EE_2.2.6_COMPOSER_v1.patch
Compatible Magento versions:
The patches were created for:
- Magento Commerce (Cloud) 2.2.3 (the
MDVA-12312_EE_2.2.3_COMPOSER_v1.patchfile) - Magento Commerce (Cloud) 2.2.6 (the
MDVA-14172_EE_2.2.6_COMPOSER_v1.patchfile)
The MDVA-12312_EE_2.2.3_COMPOSER_v1.patch patch is also compatible (but might not solve the issue) with the following Magento versions and editions:
- Magento Commerce (Cloud) 2.2.4
- Magento Commerce (Cloud) 2.2.5
- Magento Commerce 2.2.3
- Magento Commerce 2.2.4
- Magento Commerce 2.2.5
The MDVA-14172_EE_2.2.6_COMPOSER_v1.patch patch is also compatible (but might not solve the issue) with the following Magento versions and editions:
- Magento Commerce 2.2.6
How to apply the patch
See How to apply a composer patch provided by Magento for instructions.