Transactions
The Data Productivity Cloud supports Begin, Commit, and Rollback transaction components, which perform in a manner similar to the Matillion ETL equivalents. Read Transactions for more details.
The key difference to be aware of is that, while in Matillion ETL you could place and execute any component inside a transaction, in the Data Productivity Cloud only the following components will execute inside a transaction:
- Run Transform.
- SQL Script (but use with caution, because executing DDL commands will force the transaction to commit at that point).
Other components, including data ingestion components, will run outside of the transaction. This won't cause a runtime error.
This change is to avoid a Matillion ETL behavior that allowed any components to run in the transaction and could cause unexpected results, such as issuing DDL statements within a transaction that committed the transaction prematurely.
Migration path
Transactions should migrate automatically without any intervention needed; however, be aware of the behavior difference noted above. If your jobs relied on the behavior of forced commits from within the transaction, you may need to refactor as this behavior is no longer permitted.