Comparing to the Pacemaker Community Edition (CE), the Pacemaker Professional Edition (PE), comes with a timestamp detection feature.
It detects, based on the date found in the
updated_at column if the entity has changed since the last import.
The timestamp detection can be activated when invoking the appropriate import command.
To enable it, add the parameter
--use-timestamp=true when invoking the import, e.g.
vendor/bin/import-pro import:products --cache-enabled=true --use-timestamp=true
Do not forget to add the
The timestamp detection functionality has no additional configuration options.
Instead, it uses the
change-set detection configuration to query whether the `updated_at' date has changed
since the last import.
By the case of processing the primary row, and as the lines or store views, if any, is skipped.
Suppose that in many cases, where the connected PIM or ERP system is not able to provide a CSV file that only contains the deltas comparing to the last import, the timestamp detection may have a significant impact on performance, as only rows that contain changed data will be processed.
When the timestamp has been changed, further processing the import will automatically use the change-set functionality.
To avoid this, consider using the additional paramater