Handling of 3rd-Party-Indexer
Dependency Analysis
Before integrating a custom or third-party indexer into the Pacemaker pipeline, it is critical to analyze its dependencies:
-
Catalog Entity Dependencies
Verify whether the indexer depends on Magento catalog entities such as products, categories, or attributes.
-
Other Indexers
Check if the indexer requires data or synchronization with other indexers.
Ignored Indexer Configuration
If the custom or third-party indexer does not have any dependencies to catalog data, consider excluding it from Pacemaker’s pipeline using the Ignored Indexer configuration. This simplifies the pipeline and reduces unnecessary overhead.
Handling Dependencies
If the custom or third-party indexer have dependencies to catalog data, please adapt the following (or alternative) types and/or virtual types in DI.
-
-
TechDivision\PacemakerImportBase\Virtual\Condition\NoConflictingInventoryIndexingProcess -
TechDivision\PacemakerImportInventory\Virtual\Condition\NoConflictingInventoryIndexingProcess -
TechDivision\PacemakerImportBase\Virtual\Condition\NoConflictingInventoryIndexingProcess -
TechDivision\PacemakerImportCatalog\Virtual\Condition\NoConflictingCatalogIndexingProcess -
TechDivision\PacemakerImportPrice\Virtual\Condition\NoConflictingPriceIndexingProcess
-
-
-
TechDivision\PacemakerImportCatalog\Virtual\Model\Indexer\CatalogIndexSetter -
TechDivision\PacemakerImportCatalog\Virtual\Model\Indexer\ProductIndexSetter -
TechDivision\PacemakerImportCatalog\Virtual\Model\Indexer\CategoryIndexSetter -
TechDivision\PacemakerImportCustomer\Virtual\Model\Indexer\CustomerIndexSetter -
TechDivision\PacemakerImportInventory\Virtual\Model\Indexer\InventoryIndexSetter -
TechDivision\PacemakerImportPrice\Virtual\Model\Indexer\PriceIndexSetter -
TechDivision\PacemakerIndexer\Virtual\Model\CompleteIndexerSetter
-