Elasticsearch price fieldname is incorrect during indexing when storeId and websiteId do not match #21216
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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 (*)