-
Notifications
You must be signed in to change notification settings - Fork 9.3k
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
Elasticsearch price fieldname is incorrect during indexing when storeId and websiteId do not match #21216
Conversation
The method getProductPriceData expects $websiteId as a parameter, but $storeId was given. It should be $websiteId since prices are website specific. Also see \Magento\Elasticsearch\Elasticsearch5\Model\Adapter\DataMapper\ProductDataMapper where a similar method exists and $websiteId is used.
Hi @alexander-aleman. Thank you for your contribution
For more details, please, review the Magento Contributor Assistant documentation |
Hi @aleron75, thank you for the review. |
@alexander-aleman thank you for contributing. Please accept Community Contributors team invitation here to gain extended permissions for this repository. |
merge from magento/magento2
Hi @alexander-aleman, thank you for your contribution! |
…ng when storeId and websiteId do not match #21216
Description (*)
The method getProductPriceData expects $websiteId as a parameter, but $storeId was given. It should be $websiteId since prices are website specific. Also see \Magento\Elasticsearch\Elasticsearch5\Model\Adapter\DataMapper\ProductDataMapper where a similar method exists and $websiteId is used. In cases where $websiteId and $storeId are different this causes the price filter to not work because ElasticSearch contains a field $fieldName = 'price_' . $customerGroupId . '' . $storeId, but during filtering $fieldName = 'price' . $customerGroupId . '_' . $websiteId is requested.
Fixed Issues (if relevant)
Manual testing scenarios (*)
Contribution checklist (*)