Enhancements Import Pipelines
To optimize index management specifically for Pacemaker imports, there are generic steps that can be customized with Magento-DI and extended with Pipeline-XML.
The following listed steps are already integrated into the standard import pipelines of the Pacemaker.
Index Setters
The index setter is an executor/step that should be integrated into various import pipelines to get the best possible performance.
The basic logic of the index setter is the temporary writing of indexer types into the database
table Pacemaker pacemaker_indexer
.
-
This table is read in the
Force-Reindex-Step
-
The setters can be easily customized with DI per pipeline
vendor/techdivision/pacemaker-import-customer/etc/pipeline.xml
<step name="index_customer_setter"
executorType="TechDivision\PacemakerImportCustomer\Virtual\Model\Indexer\CustomerIndexSetter" sortOrder="40" description="Set index info for related indexer">
<conditions>
<step_condition type="TechDivision\ProcessPipelines\Helper\Condition\Step\AttemptsLimit\Limit1" description="Try once."/>
<step_condition type="TechDivision\ProcessPipelines\Helper\Condition\Step\PreviousStepsCompleted" description="Previous step needs to be finished."/>
</conditions>
</step>
Indexer-Spawner
The indexer-spawner is an auxiliary executor/step which can get integrated into import pipelines to ensure the creation of an index pipeline.
vendor/techdivision/pacemaker-import-customer/etc/pipeline.xml
<step name="spawn_indexer" executorType="TechDivision\PacemakerIndexer\Model\IndexerSpawnExecutor" sortOrder="99" description="Spawn new indexer pipeline after import.">
<conditions>
<step_condition type="TechDivision\ProcessPipelines\Helper\Condition\Step\AttemptsLimit\Limit1" description="Try once."/>
<step_condition type="TechDivision\ProcessPipelines\Helper\Condition\Step\PreviousStepsCompleted" description="Previous step needs to be finished."/>
</conditions>
</step>