MySQL and ElasticSearch show different results
This article provides a patch for the known Adobe Commerce on cloud infrastructure 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 the same filter 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 a note of the number of matching products.
- Configure the default MySQL search.
- On the storefront, select one of the filters.
- Make a 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 on the following links:
Compatible Adobe Commerce versions:
The patches were created for:
- Adobe Commerce on cloud infrastructure 2.2.3 (the
MDVA-12312_EE_2.2.3_COMPOSER_v1.patch
file) - Adobe Commerce on cloud infrastructure 2.2.6 (the
MDVA-14172_EE_2.2.6_COMPOSER_v1.patch
file)
The MDVA-12312_EE_2.2.3_COMPOSER_v1.patch
patch is also compatible (but might not solve the issue) with the following Adobe Commerce versions and editions:
- Adobe Commerce on cloud infrastructure 2.2.4
- Adobe Commerce on cloud infrastructure 2.2.5
- Adobe Commerce on-premises 2.2.3
- Adobe Commerce on-premises 2.2.4
- Adobe Commerce on-premises 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 Adobe Commerce versions and editions:
- Adobe Commerce on-premises 2.2.6
How to apply the patch
See How to apply a composer patch provided by Adobe in our support knowledge base for instructions.