This repository was archived by the owner on Nov 19, 2024. It is now read-only.
Added info about mview #4683
Merged
Added info about mview #4683
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
magento-engcom-team
added
Partner: Atwix
partners-contribution
|
An admin must run tests on this PR before it can be merged. |
rogyar
added
2.2.x
2.3.x
rogyar
suggested changes
Jun 5, 2019
| the indexer group. | ||
| * The `subscriptions` node is a list of tables for tracking changes. | ||
| * The `table` node defines the certain table to observe and track changes. The attribute `name` is a name of an observable table, the attribute `entity_column` is an identifier column of entity to be re-indexed. So, in case of `catalog_category_product`, whenever one or more categories is saved, updated or deleted in `catalog_category_entity` the method | ||
| execute of `Magento\Catalog\Model\Indexer\Category\Product` will be called with argument `ids` containing ids of entities from column defined |
There was a problem hiding this comment.
Suggested change
| execute of `Magento\Catalog\Model\Indexer\Category\Product` will be called with argument `ids` containing ids of entities from column defined | |
| the `execute` method of `Magento\Catalog\Model\Indexer\Category\Product` will be called with argument `ids` containing ids of entities from column defined |
| * The `subscriptions` node is a list of tables for tracking changes. | ||
| * The `table` node defines the certain table to observe and track changes. The attribute `name` is a name of an observable table, the attribute `entity_column` is an identifier column of entity to be re-indexed. So, in case of `catalog_category_product`, whenever one or more categories is saved, updated or deleted in `catalog_category_entity` the method | ||
| execute of `Magento\Catalog\Model\Indexer\Category\Product` will be called with argument `ids` containing ids of entities from column defined | ||
| under `entity_column` attribute. If indexer type is set to Update on Save the method being called right away after the operation if it set to Update by Schedule |
There was a problem hiding this comment.
Suggested change
| under `entity_column` attribute. If indexer type is set to Update on Save the method being called right away after the operation if it set to Update by Schedule | |
| under `entity_column` attribute. If indexer type is set to "Update on Save", the method is called right away after the operation. If it's set to "Update by Schedule"... |
| The table contains the `version_id` auto-increment column and `entity_id` column that contains identifiers of entities to be re-indexed. | ||
| For each `table` node the framework automatically creates MYSQL AFTER triggers for each possible event (INSERT, UPDATE, DELETE). | ||
|
|
||
| For the table `catalog_category_entity` will be created triggers with the following statements: |
There was a problem hiding this comment.
Suggested change
| For the table `catalog_category_entity` will be created triggers with the following statements: | |
| For the table `catalog_category_entity` triggers will be created with the following statements. |
|
|
||
| ``` | ||
|
|
||
| The method `Magento\Framework\Mview\ViewInterface::update` responsible for handling records in the changelog. The method is being called by CRON and |
There was a problem hiding this comment.
Suggested change
| The method `Magento\Framework\Mview\ViewInterface::update` responsible for handling records in the changelog. The method is being called by CRON and | |
| The method `Magento\Framework\Mview\ViewInterface::update` is responsible for handling records in the changelog. The method is being called by CRON and |
| ``` | ||
|
|
||
| The method `Magento\Framework\Mview\ViewInterface::update` responsible for handling records in the changelog. The method is being called by CRON and | ||
| it defines ID's to be re-indexed from the change log by last applied `version_id` and call the method `execute` for each particular indexer with |
There was a problem hiding this comment.
Suggested change
| it defines ID's to be re-indexed from the change log by last applied `version_id` and call the method `execute` for each particular indexer with | |
| it defines IDs to be re-indexed from the change log by last applied `version_id` and calls the `execute` method for each particular indexer with IDs as an argument |
jeff-matthews
removed
the
Technical
rogyar
approved these changes
Jun 6, 2019
|
running tests |
|
Hi @VitaliyBoyko, thank you for your contribution! |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Purpose of this pull request
This pull request (PR) extends information about indexing, adds information about mview.xml.
Affected DevDocs pages
whatsnew
Added information about indexing and the
mview.xmlfile.