Your feedback is important to us! Email us how we can improve these documents.
This document covers some best practices on building restartability architecture into Pentaho Data Integration (PDI) jobs and transformations. In the event of a failure, it is important to be able to restart an Extract/Transform/Load (ETL) process from where it left off. This is true whether you need to avoid duplicate entries in the target database, or you are simply seeking overall ETL efficiency and don’t want to rerun processes that completed successfully in the previous run.
Our intended audience is Pentaho ETL developers and architects.
The intention of this document is to speak about topics generally; however, these are the specific versions covered here:
|Pentaho||6.x, 7.x, 8.0|
The Components Reference in Pentaho Documentation has a complete list of supported software and hardware.