Error Elasticsearch table prefix

[mohammedTBB]

Preconditions and environment

• Magento version 2.4.5-p1
• magento/module-elasticsearch version 101.0.5

Steps to reproduce

1- Go to category page
2- Filter by price

Expected result

The page filter the products without any error.

Actual result

SQLSTATE[42S02]: Base table or view not found: 1146 Table 'magento.store' doesn't exist

Additional information

The problem comes from the file
vendor/magento/module-elasticsearch/Model/ResourceModel/Fulltext/Collection/SearchResultApplier.php:263

Possible solution:
replace the line 260
. ' AND price_index.website_id = (Select website_id FROM store WHERE store_id = '
by:
. ' AND price_index.website_id = (Select website_id FROM '. $this->collection->getTable('store') .' WHERE store_id = '

Release note

No response

Triage and priority

• Severity: S0 - Affects critical data or functionality and leaves users without workaround.
• Severity: S1 - Affects critical data or functionality and forces users to employ a workaround.
• Severity: S2 - Affects non-critical data or functionality and forces users to employ a workaround.
• Severity: S3 - Affects non-critical data or functionality and does not force users to employ a workaround.
• Severity: S4 - Affects aesthetics, professional look and feel, “quality” or “usability”.

[m2-assistant]

Hi @mohammedTBB. Thank you for your report.
To speed up processing of this issue, make sure that you provided the following information:

• Summary of the issue
• Information on your environment
• Steps to reproduce
• Expected and actual results

Make sure that the issue is reproducible on the vanilla Magento instance following Steps to reproduce. To deploy vanilla Magento instance on our environment, Add a comment to the issue:

@magento give me 2.4-develop instance - upcoming 2.4.x release

For more details, review the Magento Contributor Assistant documentation.

Add a comment to assign the issue: @magento I am working on this

To learn more about issue processing workflow, refer to the Code Contributions.

---

• Join Magento Community Engineering Slack and ask your questions in #github channel.

⚠️ According to the Magento Contribution requirements, all issues must go through the Community Contributions Triage process. Community Contributions Triage is a public meeting.

🕙 You can find the schedule on the Magento Community Calendar page.

📞 The triage of issues happens in the queue order. If you want to speed up the delivery of your contribution, join the Community Contributions Triage session to discuss the appropriate ticket.

✏️ Feel free to post questions/proposals/feedback related to the Community Contributions Triage process to the corresponding Slack Channel

[m2-assistant]

Hi @engcom-Bravo. Thank you for working on this issue.
In order to make sure that issue has enough information and ready for development, please read and check the following instruction: 👇

• 1. Verify that issue has all the required information. (Preconditions, Steps to reproduce, Expected result, Actual result).

  Details

  If the issue has a valid description, the label Issue: Format is valid will be added to the issue automatically. Please, edit issue description if needed, until label Issue: Format is valid appears.

• 2. Verify that issue has a meaningful description and provides enough information to reproduce the issue. If the report is valid, add Issue: Clear Description label to the issue by yourself.

• 3. Add Component: XXXXX label(s) to the ticket, indicating the components it may be related to.

• 4. Verify that the issue is reproducible on 2.4-develop branch

  Details

  - Add the comment @magento give me 2.4-develop instance to deploy test instance on Magento infrastructure.
  - If the issue is reproducible on 2.4-develop branch, please, add the label Reproduced on 2.4.x.
  - If the issue is not reproducible, add your comment that issue is not reproducible and close the issue and stop verification process here!

• 5. Add label Issue: Confirmed once verification is complete.

• 6. Make sure that automatic system confirms that report has been added to the backlog.

[engcom-Bravo]

Hi @mohammedTBB,

Thank you for reporting and collaboration.

Verified the issue on Magento 2.4-develop instance and the issue is not reproducible. Kindly refer the screenhsots.

We are able to filter the products with the price without any errors.

Kindly recheck the behavior on Magento 2.4-develop instance and elaborate steps to reproduce if the issue is still reproducible.

Thanks.

[mohammedTBB]

Hi engcom-Bravo,

The error appear in the frontend category page, by ordering the products by price.

Thanks.

[engcom-Bravo]

@magento give me 2.4-develop instance

[magento-deployment-service]

Hi @engcom-Bravo. Thank you for your request. I'm working on Magento instance for you.

[magento-deployment-service]

Hi @engcom-Bravo, here is your Magento Instance: https://c3319b9ff219083da6322dd181bc99db.instances.magento-community.engineering
Admin access: https://c3319b9ff219083da6322dd181bc99db.instances.magento-community.engineering/admin_c6e2
Login: d5aee3da
Password: 6ec7d318da89

[engcom-Bravo]

Hi @mohammedTBB,

Thanks for your update.

Verified the issue on Magento 2.4-develop instance and the issue is not reproducible. Kindly refer the screenhsots.

We are able to filter the products.

Kindly recheck the issue on Magento 2.4-develop instance and check if any 3rd party extensions / modules enabled is causing this issue.

Thanks.

[mohammedTBB]

Hi engcom-Bravo

Could you please sort by 'price' instead of by 'position'?
If this does not do the trick we will check our third-party plugins.

Thanks.

[engcom-Bravo]

Hi @mohammedTBB,

Thanks for your update.

Verified the issue on Magento 2.4-develop instance and the issue is not reproducible. Kindly refer the screenhsots.

We are able to sort with 'Price'.

Thanks.

[hostep]

This seems to be a similar problem as reported in #36518

@mohammedTBB: The code you referenced has been refactored significantly and this refactor will be included in Magento 2.4.6 and your issue should be fixed when it gets released on March 14. I've mentioned some details over here: #36478 (comment)

This issue can probably be closed now.

[engcom-Bravo]

Hi @hostep.

Thanks for your update.

We are closing this issue.

Thanks.