Magento\/Catalog\/etc\/mview.xml<\/em><\/p>\n<?xml version=\"1.0\" encoding=\"UTF-8\"?>\r\n<config xmlns:xsi=\"http:\/\/www.w3.org\/2001\/XMLSchema-instance\" xsi:noNamespaceSchemaLocation=\"urn:magento:framework:Mview\/etc\/mview.xsd\">\r\n…\r\n<view id=\"catalog_category_product\" class=\"Magento\\Catalog\\Model\\Indexer\\Category\\Product\" group=\"indexer\">\r\n <subscriptions>\r\n <table name=\"catalog_category_entity\" entity_column=\"entity_id\" \/>\r\n <table name=\"catalog_category_entity_int\" entity_column=\"entity_id\" \/>\r\n <\/subscriptions>\r\n<\/view>\r\n…\r\n<\/config>\r\n<\/pre>\nFrom this extract, you can see that the catalog_category_product_cl<\/strong> will be created. It will contain the information about the changes in catalog_category_entity <\/strong>and catalog_category_entity_int<\/strong> tables.<\/p>\nAll the change log tables are created by a certain INDEXER_TABLE_NAME + ‘_cl’ rule. The tables contain the version_id <\/strong>columns as autoincrement and entity_id, which<\/strong> contains the object identifier that needs to be reindexed. For every table listed in the table nodes, three types of MYSQL AFTER triggers are created: INSERT, UPDATE, DELETE.<\/p>\nFor example, for the catalog_category_entity<\/em> table, the following triggers will be created:<\/p>\nCREATE DEFINER=`******`@`%` TRIGGER trg_catalog_category_entity_after_insert AFTER INSERT ON e FOR EACH ROW\r\nBEGIN\r\nINSERT IGNORE INTO `catalog_category_product_cl` (`entity_id`) VALUES (NEW.`entity_id`);\r\nEND \r\n\r\nCREATE DEFINER=`******`@`%` TRIGGER trg_catalog_category_entity_after_update AFTER UPDATE ON e FOR EACH ROW\r\nBEGIN\r\n IF (NEW.`entity_id` <=> OLD.`entity_id`\r\n OR NEW.`attribute_set_id` <=> OLD.`attribute_set_id`\r\n OR NEW.`parent_id` <=> OLD.`parent_id`\r\n OR NEW.`created_at` <=> OLD.`created_at`\r\n OR NEW.`path` <=> OLD.`path`\r\n OR NEW.`position` <=> OLD.`position`\r\n OR NEW.`level` <=> OLD.`level`\r\n OR NEW.`children_count` <=> OLD.`children_count`)\r\n THEN INSERT IGNORE INTO `catalog_category_product_cl` (`entity_id`) VALUES (NEW.`entity_id`);\r\n END IF;\r\nEND\r\n\r\nCREATE DEFINER=`******`@`%` TRIGGER trg_catalog_category_entity_after_delete AFTER DELETE ON e FOR EACH ROW\r\nBEGIN\r\n INSERT IGNORE INTO `catalog_category_product_cl` (`entity_id`) VALUES (OLD.`entity_id`);\r\nEND\r\n<\/pre>\nThe Mview component checks version_id<\/strong> in the *_cl tables if it is different from the one stored in the mview_state<\/strong> table. If the numbers are different, reindex launches.<\/p>\nPartial and complete indexation<\/h2>\n
Here, we are going to discuss partial and complete indexation in Magento 2.<\/p>\n
Partial indexation<\/h3>\n
Partial indexation updates indexes only in the objects that were modified. Partial indexation occurs both with Update on Save<\/strong> and Update by Schedule<\/strong> index modes. It is an indexation type where the change log tables are used, which we described above.<\/p>\nComplete indexation<\/h3>\n
Complete indexation is required by some extensions in Magento 2, as some indexes may become invalid. Complete indexation launches by cron schedule<\/strong> or manually<\/strong>.<\/p>\nMagento index management FAQs<\/h2>\nHow create custom index<\/h3>\n
In order to do it, we will create a custom module. First of all, the registration.php file<\/em>:<\/p>\n<?php\r\n\\Magento\\Framework\\Component\\ComponentRegistrar::register(\r\n \\Magento\\Framework\\Component\\ComponentRegistrar::MODULE,\r\n 'Belvg_CronIndexer',\r\n __DIR__\r\n);<\/pre>\nAnd the etc\/module.xml file<\/em>:<\/p>\n<?xml version=\"1.0\"?>\r\n<config xmlns:xsi=\"http:\/\/www.w3.org\/2001\/XMLSchema-instance\"\r\n xsi:noNamespaceSchemaLocation=\"urn:magento:framework:Module\/etc\/module.xsd\">\r\n <module name=\"Belvg_CronIndexer\" setup_version=\"1.0.0\">\r\n <\/module>\r\n<\/config>\r\n<\/pre>\nSo, now we define our index. We need to create a etc\/indexer.xml<\/em> file for it:<\/p>\n<?xml version=\"1.0\"?>\r\n<config xmlns:xsi=\"http:\/\/www.w3.org\/2001\/XMLSchema-instance\" xsi:noNamespaceSchemaLocation=\"urn:magento:framework:Indexer\/etc\/indexer.xsd\">\r\n <indexer id=\"belvg_customcron_indexer\r\n\" view_id=\"belvg_customcron_indexer\r\n\" class=\"Belvg\\CronIndexer\\Model\\Indexer\\Example\">\r\n <title translate=\"true\">Belvg Indexer Example<\/title>\r\n <description translate=\"true\">Belvg custom indexer<\/description>\r\n <\/indexer>\r\n<\/config>\r\n<\/pre>\nIn this file, we define a new indexer with attributes:<\/p>\n
id<\/strong> is a new unique index identifier. It is necessary, particularly for launching reindex via the terminal.
\nview_id <\/strong>is an identifier in the mview.xml <\/strong>file.
\nclass <\/strong>possesses certain processing methods (executeFull, executeList, executeRow)<\/p>\nSimple indexer should contain the following elements:<\/p>\n
title <\/strong>of an index that will be displayed in index grid
\ndescription<\/strong> of an index that will be displayed in index grid<\/p>\nThen, we create a etc\/mview.xml <\/strong>file. It is necessary to detect changes in table objects and turn on indexers.<\/p>\n<?xml version=\"1.0\" encoding=\"UTF-8\"?>\r\n<config xmlns:xsi=\"http:\/\/www.w3.org\/2001\/XMLSchema-instance\" xsi:noNamespaceSchemaLocation=\"urn:magento:framework:Mview\/etc\/mview.xsd\">\r\n <view id=\"belvg_customcron_indexer\" class=\"Belvg\\CronIndexer\\Model\\Indexer\\Example\" group=\"indexer\">\r\n <subscriptions>\r\n <table name=\"catalog_product_entity\" entity_column=\"entity_id\" \/>\r\n <\/subscriptions>\r\n <\/view>\r\n<\/config>\r\n<\/pre>\nIn this file, we define the identifier of our mview and class where the execute() <\/strong>method will launch if there are any data changes. In the subscriptions<\/strong> node, we define the tables that contain the table name and column which value will be transferred to the execute() method if the value is changed. So when the value of entity_id will be transferred to the Belvg\\CronIndexer\\Model\\Indexer\\Example::execute()<\/strong> method if the values are changed in the catalog_product_entity<\/strong> table.<\/p>\nIn the indexer.xml<\/strong> and mview.xml<\/strong> files, we have defined the Belvg\\CronIndexer\\Model\\Indexer\\Example<\/strong> class, where the methods for changing data processing should be. Now, we need to create Model\/Indexer\/Example.php<\/strong><\/p>\n<?php\r\nnamespace Belvg\\CronIndexer\\Model\\Indexer;\r\n\r\nclass Example implements \\Magento\\Framework\\Indexer\\ActionInterface, \\Magento\\Framework\\Mview\\ActionInterface\r\n{\r\n \/*\r\n * Used by mview, allows process indexer in the \"Update on schedule\" mode\r\n *\/\r\n public function execute($ids){\r\n \/\/Used by mview, allows you to process multiple placed orders in the \"Update on schedule\" mode\r\n }\r\n\r\n \/*\r\n * Will take all of the data and reindex\r\n * Will run when reindex via command line\r\n *\/\r\n public function executeFull(){\r\n \/\/Should take into account all placed orders in the system\r\n }\r\n\r\n \/*\r\n * Works with a set of entity changed (may be massaction)\r\n *\/\r\n public function executeList(array $ids){\r\n \/\/Works with a set of placed orders (mass actions and so on)\r\n }\r\n\r\n \/*\r\n * Works in runtime for a single entity using plugins\r\n *\/\r\n public function executeRow($id){\r\n \/\/Works in runtime for a single order using plugins\r\n }\r\n}\r\n<\/pre>\nHow to make Magento 2 index automatically at a set time?<\/h3>\n
So, we need to change the indexing frequency through cron. By default, indexation is performed every minute. You can see it for yourself by opening the file vendor \/ magento \/ module-indexer \/ etc \/ crontab.xml<\/em>.<\/p>\n<?xml version=\"1.0\"?>\r\n<!--\r\n\/**\r\n* Copyright © Magento, Inc. All rights reserved.\r\n* See COPYING.txt for license details.\r\n*\/\r\n-->\r\n<config xmlns:xsi=\"http:\/\/www.w3.org\/2001\/XMLSchema-instance\" xsi:noNamespaceSchemaLocation=\"urn:magento:module:Magento_Cron:etc\/crontab.xsd\">\r\n <group id=\"index\">\r\n <job name=\"indexer_reindex_all_invalid\" instance=\"Magento\\Indexer\\Cron\\ReindexAllInvalid\" method=\"execute\">\r\n <schedule>* * * * *<\/schedule>\r\n <\/job>\r\n <job name=\"indexer_update_all_views\" instance=\"Magento\\Indexer\\Cron\\UpdateMview\" method=\"execute\">\r\n <schedule>* * * * *<\/schedule>\r\n <\/job>\r\n <job name=\"indexer_clean_all_changelogs\" instance=\"Magento\\Indexer\\Cron\\ClearChangelog\" method=\"execute\">\r\n <schedule>0 * * * *<\/schedule>\r\n <\/job>\r\n <\/group>\r\n<\/config>\r\n<\/pre>\nWe are primarily interested in the <job name = “indexer_reindex_all_invalid”> tag. Five asterisks indicate that all invalid indexes are updated every minute. Asterisks are given according to this table:<\/p>\n
* * * * * command to be executed
\n| | | | |
\n| | | | +—– Day of week (0 – 7) (Sunday=0 or 7)
\n| | | +——- Month (1 – 12)
\n| | +——— Day of the month (1 – 31)
\n| +———– Hour (0 – 23)
\n+————- Minute (0 – 59)<\/p>\n
You can also set the numerical values, with the asterisk simply meaning “every minute (hour, day, etc.)”. Therefore, if you want to update crown indexes only once a day at a certain time, you can write, for example, this: 0 4 * * *. This entry will indicate: 0 minutes – 4 hours – every day (4 am every day).<\/p>\n
But we cannot make changes to the files that the vendor folder contains. For this, you will need to create your own module. We can use the module created before Belvg_CronIndexer<\/strong>.<\/p>\nAnd now in the etc folder, we will create a crontab.xml file with the following contents:<\/p>\n
<?xml version=\"1.0\"?>\r\n<config xmlns:xsi=\"http:\/\/www.w3.org\/2001\/XMLSchema-instance\" xsi:noNamespaceSchemaLocation=\"urn:magento:module:Magento_Cron:etc\/crontab.xsd\">\r\n <group id=\"index\">\r\n <job name=\"indexer_reindex_all_invalid\" instance=\"Magento\\Indexer\\Cron\\ReindexAllInvalid\" method=\"execute\">\r\n <schedule>0 4 * * *<\/schedule>\r\n <\/job><\/group><\/config>\r\n<\/pre>\nIt overrides the default schedule so that reindexing of invalid indexes runs once daily at 4 AM rather than every minute — a particularly useful optimization for high-catalog-volume stores that have grown significantly in size.<\/p>\n
This is all to the topic of index management in Magento 2. We hope this article was helpful to you. If you have any comments or questions, please leave them down below.<\/p>\n\n
\n
\n
\n
\n ![\"Download](\"https:\/\/belvg.com\/wp-content\/uploads\/2019\/06\/pixel.png\" "\\"Magento")
\n <\/picture>\n \n
\n Download our checklist <\/div>\n
\n
Download our beautiful checklist<\/p>\n <\/div>\n
![\"Magento](\"https:\/\/belvg.com\/blog\/wp-content\/uploads\/2018\/12\/diagram.png\" "\\"Magento")
<\/a><\/p>\n![\"Magento](\"https:\/\/belvg.com\/blog\/wp-content\/uploads\/2018\/12\/index-management.png\" "\\"Magento")
<\/a><\/p>\n![\"magento](\"https:\/\/belvg.com\/blog\/wp-content\/uploads\/2018\/12\/magento-index-management-reindex-magento-2.png\" "\\"Magento")
<\/a><\/p>\n![\"Indexer](\"https:\/\/belvg.com\/blog\/wp-content\/uploads\/2018\/12\/Indexer-240px.png\" "\\"Magento")
![\"Magento](\"https:\/\/belvg.com\/blog\/wp-content\/uploads\/2018\/12\/indexer-info.png\" "\\"Magento")
<\/a><\/p>\n![\"Magento](\"https:\/\/belvg.com\/blog\/wp-content\/uploads\/2018\/12\/indexer-show-mode.png\" "\\"Magento")
<\/a><\/p>\n![\"magento](\"https:\/\/belvg.com\/blog\/wp-content\/uploads\/2018\/12\/indexer-status.png\" "\\"Magento")
<\/a><\/p>\n![\"Magento](\"https:\/\/belvg.com\/blog\/wp-content\/uploads\/2018\/12\/indexer-reset.png\" "\\"Magento")
<\/a><\/p>\n![\"Download](\"https:\/\/belvg.com\/blog\/wp-content\/uploads\/2024\/01\/Optimal_CMS-1.webp\" "\\"Magento")
\n <\/picture>\n