Fatal when using GraphQl query

[DmitrySamushchenko]

Preconditions and environment

• Magento 2.4.5
• Default Magento ElasticSearch7
• Not empty database prefix, for example "pref"

Steps to reproduce

1. Run this graphQl query:

query {
  products(filter: {category_id: {eq: "2"}}, sort: {price:ASC}, currentPage: 1) {
    items {
      ...productAttributesForListing
      ... on ConfigurableProduct {
        variants {
          __typename
        }
      }
    }
  }
}

fragment productAttributesForListing on ProductInterface {
  categories {
    breadcrumbs {
      category_name
    }
  }
}

Expected result

Results without error:

Actual result

Fatal Error:

Additional information

This error happened because the subquery
SELECT 1 FROM store_group WHERE cat_index.category_id IN (store_group.root_category_id
is missing a table prefix for store_group

See \Magento\CatalogGraphQl\Model\Resolver\Product\ProductCategories::getCategoryIdsByProduct

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 @DmitrySamushchenko. 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

[engcom-Lima]

@magento give me 2.4-develop instance

[magento-deployment-service]

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

[magento-deployment-service]

Hi @engcom-Lima, here is your Magento Instance: https://a89637121cdfe9d55db688caa6737b61.instances.magento-community.engineering
Admin access: https://a89637121cdfe9d55db688caa6737b61.instances.magento-community.engineering/admin_a428
Login: f95e18e1
Password: 702be698dd4e

[github-jira-sync-bot]

✅ Jira issue https://jira.corp.adobe.com/browse/AC-6685 is successfully created for this GitHub issue.

[m2-assistant]

✅ Confirmed by @engcom-Lima. Thank you for verifying the issue.
Issue Available: @engcom-Lima, You will be automatically unassigned. Contributors/Maintainers can claim this issue to continue. To reclaim and continue work, reassign the ticket to yourself.

[engcom-Hotel]

Hello,

As I can see this issue got fixed in the scope of the internal Jira ticket AC-6685 by the internal team
Related commits: https://github.com/magento/magento2/search?q=AC-6685&type=commits

Based on the Jira ticket, the target version is 2.4.6.

Thanks