When you configure a JDBC V2 mapping in advanced mode to read from or write data to a database that supports the Type 4 JDBC driver, you can configure partitioning for the JDBC V2 source or target to optimize the mapping in advanced mode performance at run time. The partition type controls how the advanced cluster distributes data among partitions at partition points.
The advanced cluster distributes rows of data based on the partition key you define. Before you configure a partition, ensure that you select the partition key in the Fields tab of the Source or Target transformation in a JDBC V2 mapping. If the imported table already has a primary key defined, the cluster application considers that as the default partition key. Before you import, ensure that the table has only one partition key.
After you import, you can change the partition key on the Fields tab. From the Options list, select Edit Metadata and then select the partition key. Ensure that you do not define more than one partition key for the source or target.
The default number of partitions is 1. If the number of partitions you specified for the target is 1, the cluster application considers the same number of partitions you specified for the source as the target partition number.
JDBC V2 data types supported for partitioning
The following table lists the JDBC V2 data types supported as partition keys: