-
Notifications
You must be signed in to change notification settings - Fork 9.4k
[Issue] Set default indexer mode to 'schedule' #36419
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
Unfortunately, not enough information was provided to create a Jira ticket. Please make sure you added the following label(s): Once all required labels are present, please add |
✅ Jira issue https://jira.corp.adobe.com/browse/AC-6975 is successfully created for this GitHub issue. |
✅ Confirmed by @engcom-Lima. Thank you for verifying the issue. |
re-opened because of #36347 (comment) #36347 (comment) |
Hi @fredden, Thanks for your Contribution!! As per the requirement of https://jira.corp.adobe.com/browse/AC-6975 we delivered ‘Indexer default mode was schedule after Magento installation only’ and was not working when we install third-party Indexer(Custom Indexer) as default mode was still on save with third-party Indexer(Custom Indexer) Related commits: https://github.com/search?q=repo%3Amagento%2Fmagento2+Arrows_Delivery_07022024&type=commits Based on the Jira ticket, the target version is 2.4.8-beta1. Thanks |
This issue is automatically created based on existing pull request: #36347: Set default indexer mode to 'schedule'
Description
It is recommended that indexers be in the
schedule
("Update by Schedule") mode, and notrealtime
("Update on Save") mode. However, when Magento is installed for the first time, all indexers are by default in the "wrong" mode. This pull request changes the default for new indexers to be in the expected / recommended mode.This change will not impact any existing indexers and therefore existing websites should not notice any impact from this change. If a module with an indexer is installed on an existing website, it will be created with the new default mode: {{{}schedule{}}}.
Manual testing scenarios
The text was updated successfully, but these errors were encountered: