-
Notifications
You must be signed in to change notification settings - Fork 340
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Category product index is wrong after switching to temptables for indexing. #622
Comments
We have reverted the use temp table option but the issue persists, I suspect this is unrelated to the temptables change. |
Do not see what you mean by : "switching to temptables for indexing". |
We tried to use the fix suggested the problem mentioned here. magento/magento2#10591
|
Hi @Diadara , We won't support the patch suggested in magento/magento2#10591 until it will be an official one. Once Magento code is reverted to the original, have you tried :
BR, |
Another idea on this one : are you sharing the same ES server between multiple environment (testing, staging and production). If so take care to use a different index alias name between the environment in the ES config section. See the doc here : https://github.com/Smile-SA/elasticsuite/wiki/ModuleInstall#indices-settings |
We are using separate servers for our staging environments and we have tried reverting the patch and reindexing and clearing caches without success. Will it be possible for someone from your team to have a look at the staging environment or check our db dump. The mysql catalog indexes are fine and don't have an issue, but the elastic cache indexes are still wrong. |
Our team can have a look as part of our paid commercial support if you want a faster resolution of the issue. BR, |
This patch solve only the issue of empty categories when index category products is in progress. |
The issue was not caused by the temptables patch as we initially thought. I did some digging around and discovered that we had a child virtual category as one of the leaf categories of the category in question which did not have a root category selected. This caused the query builder to work in an unexpected way to create an empty query that selects all products, and all the all the parent categories go filled with irrelevant results. You could have a validation step to prevent activating virtual categories without a parent category or modify the query builder to not select everything in the catalog, if no root category is selected. |
The feature works as designed and as expected for me. When creating a virtual category without root and no filter, the whole catalog is used.
|
PR have been merged in branches 2.4.x and master. |
Preconditions
Magento Version: 2.1.9
ElasticSuite Version: 2.3.10
Environment: production
Third party modules :
Steps to reproduce
We are currently using Magento 2.1.9 with elasticsuite 2.3. with data migrated from Magento 1.8.1 with index on save turned on. We have noticed that some of the newly created products are indexed into the wrong categories. We have double checked the category tables and Magento's index tables and found them to be correct. However, our newly created products still appear in the wrong categories.
Expected result
Products should only appear on their respective categories
Actual result
We are seeing products in the wrong categories in frontend and in the admin panel preview for the category.
The text was updated successfully, but these errors were encountered: