Skip to content
This repository was archived by the owner on Nov 19, 2024. It is now read-only.

Commit 80685e0

Browse files
atwixfirsterkeharper
atwixfirster
authored and
keharper
committed
magento/devdocs#: Fix links in How Magento implements indexing (#5656)
https://devdocs.magento.com/guides/v2.2/extension-dev-guide/indexing.html https://devdocs.magento.com/guides/v2.3/extension-dev-guide/indexing.html
1 parent bbcb56e commit 80685e0

File tree

2 files changed

+62
-52
lines changed

2 files changed

+62
-52
lines changed

‎guides/v2.2/extension-dev-guide/indexing.md

Lines changed: 31 additions & 26 deletions
Original file line numberDiff line numberDiff line change
@@ -31,37 +31,42 @@ This topic provides a high level description of how indexing is implemented from
3131
The following components are involved in the indexing process:
3232

3333
<table>
34-
<tbody>
35-
<tr>
36-
<th>Component</th>
37-
<th>Description</th>
38-
</tr>
39-
<tr>
40-
<td><a href="{{ site.mage2bloburl }}/{{ page.guide_version }}/app/code/Magento/Indexer" target="_blank">Magento_Indexer</a></td>
41-
<td>Implements:<ul>
42-
<li>indexer declaration</li>
43-
<li>indexer running</li>
44-
<li>indexer running mode configuration</li>
45-
<li>indexer status</li></ul></td>
46-
</tr>
47-
<tr>
48-
<td><a href="{{ site.mage2bloburl }}/{{ page.guide_version }}/lib/internal/Magento/Framework/Mview" target="_blank">Magento\Framework\Mview</a></td>
49-
<td><ul>
50-
<li>Allows tracking database changes for a certain [entity](https://glossary.magento.com/entity) (product, [category](https://glossary.magento.com/category), etc.) and running change handler.</li>
51-
<li>Emulates the <a href="http://en.wikipedia.org/wiki/Materialized_view" target="_blank">materialized view</a> technology for MySQL using triggers and separate materialization process (provides executing [PHP](https://glossary.magento.com/php) code instead of SQL queries, which allows materializing multiple queries).</li></ul></td>
52-
</tr>
53-
</tbody></table>
54-
55-
{: .bs-callout .bs-callout-warning }
34+
<tbody>
35+
<tr>
36+
<th>Component</th>
37+
<th>Description</th>
38+
</tr>
39+
<tr>
40+
<td><a href="{{ site.mage2bloburl }}/{{ page.guide_version }}/app/code/Magento/Indexer" target="_blank">Magento_Indexer</a></td>
41+
<td>Implements:
42+
<ul>
43+
<li>indexer declaration</li>
44+
<li>indexer running</li>
45+
<li>indexer running mode configuration</li>
46+
<li>indexer status</li>
47+
</ul>
48+
</td>
49+
</tr>
50+
<tr>
51+
<td><a href="{{ site.mage2bloburl }}/{{ page.guide_version }}/lib/internal/Magento/Framework/Mview" target="_blank">Magento\Framework\Mview</a></td>
52+
<td>
53+
<ul>
54+
<li>Allows tracking database changes for a certain <a href="https://glossary.magento.com/entity" target="_blank">entity</a> (product, <a href="https://glossary.magento.com/category" target="_blank">category</a>, etc.) and running change handler.</li>
55+
<li>Emulates the <a href="http://en.wikipedia.org/wiki/Materialized_view" target="_blank">materialized view</a> technology for MySQL using triggers and separate materialization process (provides executing <a href="https://glossary.magento.com/php" target="_blank">PHP</a> code instead of SQL queries, which allows materializing multiple queries).</li>
56+
</ul>
57+
</td>
58+
</tr>
59+
</tbody>
60+
</table>
61+
62+
{: .bs-callout-warning }
5663
`Magento_Indexer` replaces the Magento 1.x `Magento_Index` module. Use `Magento_Indexer` for all new development.
5764

5865
### Indexing types
5966

6067
Each index can perform the following types of reindex operations:
6168

62-
* Full reindex, which means rebuilding all the indexing-related database tables
63-
Full reindexing can be caused by a variety of things, including creating a new web store or new customer group.
64-
You can optionally fully reindex at any time using the [command line]({{ page.baseurl }}/config-guide/cli/config-cli-subcommands-index.html).
69+
* Full reindex, which means rebuilding all the indexing-related database tables. Full reindexing can be caused by a variety of things, including creating a new web store or new customer group. You can optionally fully reindex at any time using the [command line]({{ page.baseurl }}/config-guide/cli/config-cli-subcommands-index.html).
6570

6671
* Partial reindex, which means rebuilding the database tables only for the things that changed (like changing a single product attribute or price)
6772

@@ -88,7 +93,7 @@ Reindexing can be performed in two modes:
8893
* Update on Save - index tables are updated immediately after the dictionary data is changed.
8994
* Update by Schedule - index tables are updated by cron job according to the configured schedule.
9095

91-
{:.bs-callout .bs-callout-info}
96+
{: .bs-callout-info }
9297
**Update by Schedule** does not support the `customer_grid` indexer. You must either use **Update on Save** or reindex the customer grid manually (`bin/magento indexer:reindex customer_grid`). See the [Help Center article](https://support.magento.com/hc/en-us/articles/360025481892-New-customer-records-are-not-displayed-in-the-Customers-grid-after-importing-them-from-CSV).
9398

9499
To set these options:

‎guides/v2.3/extension-dev-guide/indexing.md

Lines changed: 31 additions & 26 deletions
Original file line numberDiff line numberDiff line change
@@ -31,37 +31,42 @@ This topic provides a high level description of how indexing is implemented from
3131
The following components are involved in the indexing process:
3232

3333
<table>
34-
<tbody>
35-
<tr>
36-
<th>Component</th>
37-
<th>Description</th>
38-
</tr>
39-
<tr>
40-
<td><a href="{{ site.mage2bloburl }}/{{ page.guide_version }}/app/code/Magento/Indexer" target="_blank">Magento_Indexer</a></td>
41-
<td>Implements:<ul>
42-
<li>indexer declaration</li>
43-
<li>indexer running</li>
44-
<li>indexer running mode configuration</li>
45-
<li>indexer status</li></ul></td>
46-
</tr>
47-
<tr>
48-
<td><a href="{{ site.mage2bloburl }}/{{ page.guide_version }}/lib/internal/Magento/Framework/Mview" target="_blank">Magento\Framework\Mview</a></td>
49-
<td><ul>
50-
<li>Allows tracking database changes for a certain [entity](https://glossary.magento.com/entity) (product, [category](https://glossary.magento.com/category), etc.) and running change handler.</li>
51-
<li>Emulates the <a href="http://en.wikipedia.org/wiki/Materialized_view" target="_blank">materialized view</a> technology for MySQL using triggers and separate materialization process (provides executing [PHP](https://glossary.magento.com/php) code instead of SQL queries, which allows materializing multiple queries).</li></ul></td>
52-
</tr>
53-
</tbody></table>
54-
55-
{: .bs-callout-warning }
34+
<tbody>
35+
<tr>
36+
<th>Component</th>
37+
<th>Description</th>
38+
</tr>
39+
<tr>
40+
<td><a href="{{ site.mage2bloburl }}/{{ page.guide_version }}/app/code/Magento/Indexer" target="_blank">Magento_Indexer</a></td>
41+
<td>Implements:
42+
<ul>
43+
<li>indexer declaration</li>
44+
<li>indexer running</li>
45+
<li>indexer running mode configuration</li>
46+
<li>indexer status</li>
47+
</ul>
48+
</td>
49+
</tr>
50+
<tr>
51+
<td><a href="{{ site.mage2bloburl }}/{{ page.guide_version }}/lib/internal/Magento/Framework/Mview" target="_blank">Magento\Framework\Mview</a></td>
52+
<td>
53+
<ul>
54+
<li>Allows tracking database changes for a certain <a href="https://glossary.magento.com/entity" target="_blank">entity</a> (product, <a href="https://glossary.magento.com/category" target="_blank">category</a>, etc.) and running change handler.</li>
55+
<li>Emulates the <a href="http://en.wikipedia.org/wiki/Materialized_view" target="_blank">materialized view</a> technology for MySQL using triggers and separate materialization process (provides executing <a href="https://glossary.magento.com/php" target="_blank">PHP</a> code instead of SQL queries, which allows materializing multiple queries).</li>
56+
</ul>
57+
</td>
58+
</tr>
59+
</tbody>
60+
</table>
61+
62+
{: .bs-callout-warning }
5663
`Magento_Indexer` replaces the Magento 1.x `Magento_Index` module. Use `Magento_Indexer` for all new development.
5764

5865
### Indexing types
5966

6067
Each index can perform the following types of reindex operations:
6168

62-
* Full reindex, which means rebuilding all the indexing-related database tables
63-
Full reindexing can be caused by a variety of things, including creating a new web store or new customer group.
64-
You can optionally fully reindex at any time using the [command line]({{ page.baseurl }}/config-guide/cli/config-cli-subcommands-index.html).
69+
* Full reindex, which means rebuilding all the indexing-related database tables. Full reindexing can be caused by a variety of things, including creating a new web store or new customer group. You can optionally fully reindex at any time using the [command line]({{ page.baseurl }}/config-guide/cli/config-cli-subcommands-index.html).
6570

6671
* Partial reindex, which means rebuilding the database tables only for the things that changed (like changing a single product attribute or price)
6772

@@ -88,7 +93,7 @@ Reindexing can be performed in two modes:
8893
* Update on Save - index tables are updated immediately after the dictionary data is changed.
8994
* Update by Schedule - index tables are updated by cron job according to the configured schedule.
9095

91-
{:.bs-callout .bs-callout-info}
96+
{: .bs-callout-info }
9297
**Update by Schedule** does not support the `customer_grid` indexer. You must either use **Update on Save** or reindex the customer grid manually (`bin/magento indexer:reindex customer_grid`). See the [Help Center article](https://support.magento.com/hc/en-us/articles/360025481892-New-customer-records-are-not-displayed-in-the-Customers-grid-after-importing-them-from-CSV).
9398

9499
To set these options:

0 commit comments

Comments
 (0)