Skip to content

[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

Closed
m2-assistant bot opened this issue Nov 4, 2022 · 8 comments
Closed

[Issue] Set default indexer mode to 'schedule' #36419

m2-assistant bot opened this issue Nov 4, 2022 · 8 comments
Assignees
Labels
Area: Admin UI Component: Indexer Issue: On Hold Priority: P1 Once P0 defects have been fixed, a defect having this priority is the next candidate for fixing. Priority: P2 A defect with this priority could have functionality issues which are not to expectations. Progress: done Reported on 2.4.x Indicates original Magento version for the Issue report.

Comments

@m2-assistant
Copy link

m2-assistant bot commented Nov 4, 2022

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 not realtime ("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

  1. Install Magento anew
  2. Navigate in the admin to System -> Tools -> Index Management
  3. Notice the colour of the "Mode" column. Before this change, these were all red, indicating an error/problem; after this change these are all green, indicating that all is well.
@m2-community-project m2-community-project bot added Issue: ready for confirmation Priority: P1 Once P0 defects have been fixed, a defect having this priority is the next candidate for fixing. labels Nov 4, 2022
@engcom-Lima engcom-Lima added the Issue: Confirmed Gate 3 Passed. Manual verification of the issue completed. Issue is confirmed label Nov 4, 2022
@github-jira-sync-bot
Copy link

Unfortunately, not enough information was provided to create a Jira ticket. Please make sure you added the following label(s): Reproduced on 2.4.x, ^Area:.*

Once all required labels are present, please add Issue: Confirmed label again.

@github-jira-sync-bot github-jira-sync-bot removed the Issue: Confirmed Gate 3 Passed. Manual verification of the issue completed. Issue is confirmed label Nov 4, 2022
@engcom-Lima engcom-Lima added Component: Indexer Reproduced on 2.4.x The issue has been reproduced on latest 2.4-develop branch Reported on 2.4.x Indicates original Magento version for the Issue report. Area: Admin UI Issue: Confirmed Gate 3 Passed. Manual verification of the issue completed. Issue is confirmed labels Nov 4, 2022
@github-jira-sync-bot
Copy link

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

@m2-assistant
Copy link
Author

m2-assistant bot commented Nov 4, 2022

✅ 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.

@ihor-sviziev ihor-sviziev reopened this Oct 17, 2023
@m2-community-project m2-community-project bot added Progress: PR in progress and removed Issue: Confirmed Gate 3 Passed. Manual verification of the issue completed. Issue is confirmed Reproduced on 2.4.x The issue has been reproduced on latest 2.4-develop branch Progress: done Issue: ready for confirmation labels Oct 17, 2023
@ihor-sviziev
Copy link
Contributor

re-opened because of #36347 (comment) #36347 (comment)

@github-jira-sync-bot github-jira-sync-bot added Priority: P2 A defect with this priority could have functionality issues which are not to expectations. and removed Priority: P1 Once P0 defects have been fixed, a defect having this priority is the next candidate for fixing. labels Feb 28, 2024
@github-jira-sync-bot github-jira-sync-bot added the Progress: PR Created Indicates that Pull Request has been created to fix issue label Mar 15, 2024
@m2-community-project m2-community-project bot added Progress: ready for dev Priority: P1 Once P0 defects have been fixed, a defect having this priority is the next candidate for fixing. and removed Progress: PR Created Indicates that Pull Request has been created to fix issue Progress: PR in progress Progress: ready for grooming labels Jul 2, 2024
@engcom-Hotel engcom-Hotel moved this to Pull Request In Progress in High Priority Backlog Aug 19, 2024
@engcom-Bravo
Copy link
Contributor

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)
With new changes which are delivered in scope of https://jira.corp.adobe.com/browse/AC-11421 , if we install Magento or install third party Indexer(Custom Indexer), default mode will be schedule by default. It should resolve the issue raised in #36347 as well.

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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Area: Admin UI Component: Indexer Issue: On Hold Priority: P1 Once P0 defects have been fixed, a defect having this priority is the next candidate for fixing. Priority: P2 A defect with this priority could have functionality issues which are not to expectations. Progress: done Reported on 2.4.x Indicates original Magento version for the Issue report.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

6 participants