catalog_url_rewrite_product_category table missing PK

[siliconalchemy]

The catalog_url_rewrite_product_category table is missing a PK. Because of this, it cannot be replicated reliably in Galera based systems (eg. MariaDB, Percona XtradbCluster). It appears to be the only table without a PK. This is more of a problem with PXC 5.7 as it recommends enforcing strict mode which will actively break usage of this table.

Magento 2.1.5
Mysql: Percona XtraDBCluster 5.7

Preconditions

Magento 2.4-develop

Steps to reproduce

1. Open database table catalog_url_rewrite_product_category
2. Check if the table has a Primary Key

Expected result

The database table catalog_url_rewrite_product_category has Primary Key

Actual result

The database table catalog_url_rewrite_product_category doesn't have Primary Key

[veloraven]

@siliconalchemy please, format this issue according to the Issue reporting guidelines: with steps to reproduce, actual result and expected result.

[siliconalchemy]

Did you read this? How much more specific do you want it to be? Never mind, you can leave your (buggy) project buggy (ier).

[korostii]

Hi @veloraven, @magento-team,
The description seems quite extensive. Could you maybe pass this along to someone having some technical expertise in this field?

[ihor-sviziev]

@engcom-Golf @engcom-Alfa could you double check if this issue still valid, as we're having bugfix for this issue in #25746?

[stale]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed after 14 days if no further activity occurs. Thank you for your contributions.

[siliconalchemy]

Go away stalebot, this is still a valid issue.

[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]

Hello @siliconalchemy

Thank you for your report.

We Confirm that the issue is still valid on 2.4-develop, and we have added Precondition, Steps to reproduce, ER and AR to the description.

[magento-engcom-team]

✅ Confirmed by @engcom-Bravo
Thank you for verifying the issue. Based on the provided information internal tickets MC-40317 were created

Issue Available: @engcom-Bravo, You will be automatically unassigned. Contributors/Maintainers can claim this issue to continue. To reclaim and continue work, reassign the ticket to yourself.

[zakdma]

This bug was fixed in scope of internal issue B2B-1663
ece2528

[zakdma]

@siliconalchemy it fixed

[magento-engcom-team]

Hi @siliconalchemy.

Thank you for your report and collaboration!

The related internal Jira ticket MC-40317 was closed as Fixed.

The fix will be available with the upcoming 2.4.3 release.

[ihor-sviziev]

@zakdma @joanhe, please check the #33770 that was caused by the fix ece2528, maybe you could provide some workaround?