Clean up catalogrule_product_price_replica table

[fredden]

Description

There was a bug which caused the catalogrule_product_price_replica table to become unnecessarily large. The bug causing the growth has been resolved in Magento version 2.4.4 - see #31752 (comment).

This schema patch cleans up the damage done by that bug on existing websites. Deleting all entries from this table is safe.

See #31752 for details.

Related Pull Requests

• These were added directly without using a pull request: https://github.com/magento/magento2/search?q=MC-41807&type=commits - 6e6fff2, 6a9f447

Fixed Issues

• Fixes Partial Catalog Product Price Indexing not removing old price date and is extremely slow if store has many products (above 200k) #31752

Manual testing scenarios

There should be no change to any functionality after applying these changes. This is a data clean-up task.

Questions or comments

None

Contribution checklist

• Pull request has a meaningful description of its purpose
• All commits are accompanied by meaningful commit messages
• All new or changed code is covered with unit/integration tests (if applicable)
• README.md files for modified modules are updated and included in the pull request if any README.md predefined sections require an update
• All automated tests passed successfully (all builds are green)

[m2-assistant]

Hi @fredden. Thank you for your contribution
Here are some useful tips how you can test your changes using Magento test environment.
Add the comment under your pull request to deploy test or vanilla Magento instance:

• @magento give me test instance - deploy test instance based on PR changes
• @magento give me 2.4-develop instance - deploy vanilla Magento instance

❗ Automated tests can be triggered manually with an appropriate comment:

• @magento run all tests - run or re-run all required tests against the PR changes
• @magento run <test-build(s)> - run or re-run specific test build(s)
  For example: @magento run Unit Tests

<test-build(s)> is a comma-separated list of build names. Allowed build names are:

1. Database Compare
2. Functional Tests CE
3. Functional Tests EE,
4. Functional Tests B2B
5. Integration Tests
6. Magento Health Index
7. Sample Data Tests CE
8. Sample Data Tests EE
9. Sample Data Tests B2B
10. Static Tests
11. Unit Tests
12. WebAPI Tests
13. Semantic Version Checker

You can find more information about the builds here

ℹ️ Run only required test builds during development. Run all test builds before sending your pull request for review.

For more details, review the Magento Contributor Guide documentation.

⚠️ According to the Magento Contribution requirements, all Pull Requests 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 Pull Requests 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

[magento-automated-testing]

The requested builds are added to the queue. You should be able to see them here within a few minutes. Please re-request them if they don't show in a reasonable amount of time.

[ihor-sviziev]

Hi @engcom-Hotel,
I think such change should have P2 priority as it's basically wasn't fully fixed in #31752 (comment).

[ihor-sviziev]

@magento run Functional Tests B2B, Magento Health Index, Unit Tests

PS: I think adding a new data patch shouldn't cause MHI failure, so that I would treat it as a false positive.

[magento-automated-testing]

The requested builds are added to the queue. You should be able to see them here within a few minutes. Please re-request them if they don't show in a reasonable amount of time.

[ihor-sviziev]

✔ Approved.

Failing tests look not related to changes from this PR.

[magento-engcom-team]

Hi @ihor-sviziev, thank you for the review.
ENGCOM-9399 has been created to process this Pull Request

[engcom-Charlie]

As we got the approval for Magento Health Index test failure for JIRA, moving this PR to Merge in Progress.

Thank you!

[ishakhsuvarov]

@magento run all tests

[magento-automated-testing]

The requested builds are added to the queue. You should be able to see them here within a few minutes. Please re-request them if they don't show in a reasonable amount of time.

[hostep]

Hi guys, what would be the status here? Would love to see this being merged. But it's been pretty quiet here since a few months 🙂

[magento-automated-testing]

The requested builds are added to the queue. You should be able to see them here within a few minutes. Please re-request them if they don't show in a reasonable amount of time.

[ishakhsuvarov]

@magento run all tests

[magento-automated-testing]

The requested builds are added to the queue. You should be able to see them here within a few minutes. Please re-request them if they don't show in a reasonable amount of time.

[ishakhsuvarov]

@hostep Trying to get it updated and going again.

Still needs a Health Check build figured out so will definitely take extra time.

[engcom-Charlie]

Got required approvals for positive case of Magento Health Index test in JIRA hence moving it to Merge in Progress.

Thank you!

[magento-automated-testing]

The requested builds are added to the queue. You should be able to see them here within a few minutes. Please re-request them if they don't show in a reasonable amount of time.

[magento-automated-testing]

The requested builds are added to the queue. You should be able to see them here within a few minutes. Please re-request them if they don't show in a reasonable amount of time.