When you configure a mapping with multiple data flows, sources in different flows can have a different number of partitions.

Previously, sources in different flows had to have the same number of partitions.

If you send a pull request and it fails for any reason after initialization, you can find the pull status and error in the source control logs or by sending a sourceControlAction request.

Previously, if you sent a pull request and the object couldn't be found in the repository, the pull operation returned the pull status and error in the response body and excluded it from the source control logs. All other failures were visible in the source control logs.

Pushdown optimization has been renamed to SQL ELT optimization in the user interface and documentation.

The user interface includes this change in many places, including the following instances:

In the Mapping Designer, the Pushdown Optimization panel is now called the SQL ELT Optimization panel. Use the SQL ELT Optimization panel to perform SQL ELT optimization preview and SQL ELT optimization data preview.
In the mapping task wizard and the mapping task editor, the
Pushdown Optimization
property is now called
SQL ELT Optimization
.
When you use CLAIRE-powered runtime strategies, CLAIRE might recommend using SQL ELT optimization to run the mapping.
In the job details for a mapping task, the Pushdown Optimization area is now called SQL ELT Optimization.

For more information about SQL ELT optimization, see

Tasks

. For more information about SQL ELT optimization preview, see

Mappings

. For more information about monitoring mapping tasks, see the Monitor help.

The Hierarchy Parser transformation always generates primary and foreign keys sequentially starting from 1.

Previously, the transformation didn't generate keys in sequential order in some cases.

On the

Advanced

tab, the

Disabled concurrent execution

option to disable the concurrent taskflow execution is renamed to

Skip if Running

.