A newer version of this documentation is available: View the Latest Version

Timestamp detection

Compared to Pacemaker Community Edition, the Pacemaker Professional Edition contains a timestamp detection feature.

This feature detects if the entity has changed since the last import based on the date in the updated_at column.

Configuration

The timestamp detection feature has no additional configuration options
The change-set detection configuration gets used to query whether the updated_at date has changed since the last import; If any, when processing the primary row and rows of memory views, this gets skipped

Option Default Description

--use-timestamp

false

Activate/deactivate the Timestamp detection

true | false

If the timestamp has changed, further processing of the import will automatically use the change-set functionality.

It is recommended to use the additional parameter --use-change-set=false.

If the option --use-timestamp is active, add the --cache-enabled=true parameter; otherwise, the performance will reduce significantly.

In many cases, the connected PIM or ERP system is not able to provide a CSV file containing only the deltas compared to the last import.

The timestamp detection can significantly impact performance since only rows containing changed data are processed

Console

The Timestamp detection can get enabled by calling the corresponding import command.

Example

To activate the Timestamp detection, add the additional parameter --use-timestamp=true to the CLI command when calling the import:

vendor/bin/import-pro import:products --cache-enabled=true --use-timestamp=true

Timestamp detection

Configuration

Console

Example

WIR HÄTTEN IHNEN DIESE MELDUNG AUCH GERNE ERSPART ...