Table of Contents

Search

  1. Preface
  2. Transformations
  3. Source transformation
  4. Target transformation
  5. Access Policy transformation
  6. Aggregator transformation
  7. B2B transformation
  8. Chunking transformation
  9. Cleanse transformation
  10. Data Masking transformation
  11. Data Services transformation
  12. Deduplicate transformation
  13. Expression transformation
  14. Filter transformation
  15. Hierarchy Builder transformation
  16. Hierarchy Parser transformation
  17. Hierarchy Processor transformation
  18. Input transformation
  19. Java transformation
  20. Java transformation API reference
  21. Joiner transformation
  22. Labeler transformation
  23. Lookup transformation
  24. Machine Learning transformation
  25. Mapplet transformation
  26. Normalizer transformation
  27. Output transformation
  28. Parse transformation
  29. Python transformation
  30. Rank transformation
  31. Router transformation
  32. Rule Specification transformation
  33. Sequence transformation
  34. Sorter transformation
  35. SQL transformation
  36. Structure Parser transformation
  37. Transaction Control transformation
  38. Union transformation
  39. Vector Embedding transformation
  40. Velocity transformation
  41. Verifier transformation
  42. Web Services transformation

Transformations

Transformations

Partitioning examples

Partitioning examples

The following examples show how you can configure partitioning in a mapping.

Partitioning with a Flat File Source

You have a
mapping
task that uses a large, 1GB flat file source. You want to specify two partitions in the Source transformation to optimize performance.
On the
Partitions
tab for the Source transformation, you select fixed partitioning and enter the number of partitions, as shown in the following image:
On the Partitions tab of the Source transformation, the partitioning type is "Fixed" and the number of partitions is set to "2."

Key Range Partitioning with a Relational Database Source

You have customer names, addresses, and purchasing history in a relational database source. You decide to partition the source data into three partitions based on postal codes, using the following ranges:
  • First partition: Minimum value to 30000
  • Second partition: 30000 to 50000
  • Third partition: 50000 to maximum value
On the
Partitions
tab for the Source transformation, you select key range partitioning and choose the BILLINGPOSTALCODE field as the partition key. You add three key ranges to create three partitions, as shown in the following image:
On the Partitions tab for the Source transformation, the partitioning type is "Key Range" and the BILLINGPOSTALCODE column is selected as the partition key. The Start Range and End Range columns for each partition define the range of values for each partition. In the first partition, the start range is blank, so the minimum value is used as the starting value. In the third partition, the end range is blank, so the maximum value is used as the ending value.
Note that for the first partition, you leave the start value blank for the minimum value. In the last partition, you leave the end value blank for the maximum value.
Using these values, records with a postal code of 0 up to 30000 are processed in partition #1, records with a postal code of 30000 to 50000 are processed in partition #2, and records with a postal code of 50000 or higher are processed in partition #3.
After you configure the mapping, you save and run the mapping to validate the partitions.

0 COMMENTS

We’d like to hear from you!