The October 2026 release of Data Ingestion and Replication includes the following changed behavior.
Enhanced Query-based CDC logic to release task units faster and reduce queuing time
For database ingestion and replication combined initial and incremental load tasks that have a Db2 for LUW, Oracle, or SQL Server source and use the query-based CDC method, a new dynamic algorithm triggers a CDC cycle as soon as one or more tables complete their initial load and releases the task unit for those tables sooner. During this initial period, CDC cycles might run at shorter, dynamic intervals. After all tables reach a normal state, the task returns to the CDC interval that you configured.
Previously, the task didn't release the task unit for a table until a full CDC cycle completed. This behavior caused tables that had finished unloading to remain in backlog status for hours if you configured a long CDC interval with a low Max Task Units value.
New parameter for encryptText command in Data Ingestion and Replication Command-Line Interface
When you encrypt a text value with the encryptText command in the Data Ingestion and Replication Command-Line Interface, you must now specify an encryption method with the --method parameter: Available options are:
•keystore. Legacy value. The encryption key is stored in a key-store.txt file
•selfcontained. New value. The encryption key is embedded in the encrypted output, making the encrypted value portable without requiring a separate key file.
Previously, the keystore encryption method was the only available option and the encryptText command did not include a method parameter.
Number of Rows in Output File field location
For application ingestion and replication tasks and database ingestion and replication tasks, the Number of Rows in Output File field has moved from the Advanced Options section to the Custom Properties section on the Let's Go! page of the task configuration wizard. If you don't select a value, a default of 100000 rows is applied. For tasks that are already deployed, the field appears in the Custom Properties section and is pre-populated with the value saved at deploy time.
Updated names for Google Cloud Storage V2 connection properties
The Google Cloud Storage V2 connection properties now use the names Service Account Private Key ID and Service Account Client ID. Previously, these connection properties had the names Private Key ID and Client ID. The name change doesn't affect existing connections or upgrades.