Table of Contents

Search

  1. Preface
  2. Transformations
  3. Source transformation
  4. Target transformation
  5. Aggregator transformation
  6. Cleanse transformation
  7. Data Masking transformation
  8. Deduplicate transformation
  9. Expression transformation
  10. Filter transformation
  11. Hierarchy Builder transformation
  12. Hierarchy Parser transformation
  13. Input transformation
  14. Java transformation
  15. Java transformation API reference
  16. Joiner transformation
  17. Lookup transformation
  18. Mapplet transformation
  19. Normalizer transformation
  20. Output transformation
  21. Parse transformation
  22. Rank transformation
  23. Router transformation
  24. Rule Specification transformation
  25. Sequence Generator transformation
  26. Sorter transformation
  27. SQL transformation
  28. Structure Parser transformation
  29. Transaction Control transformation
  30. Union transformation
  31. Verifier transformation
  32. Web Services transformation

Transformations

Transformations

Partitions

Partitions

If your organization has the Partitioning license, you can use partitions to optimize performance for
mapping
tasks.
If a
mapping
task processes large data sets or includes transformations that perform complicated calculations, the task can take a long time to process. When you use multiple partitions, the
mapping
task divides data into partitions and processes the partitions concurrently, which can optimize performance.
Enable partitioning when you configure the Source transformation in the Mapping Designer. When you configure partitions in the Source transformation, partitioning occurs throughout the mapping.
Use one of the following partitioning methods based on the source type:
Specify a key range.
Use this method for a mapping with a relational source. When you enable partitioning using a key range, the
mapping
task distributes rows of data based on a field that you define as a partition key. You select one field in the source as the partition key. Then you define a range of values for the partition key.
Key ranges can be of the following data types:
  • String
  • Any type of number data type. However, you cannot use decimals in key range values.
  • Date/time type. Use the following format:
    MM/DD/YYYY HH24:MI:SS
If the mapping includes multiple sources, use the same number of key ranges for each source.
Specify the number of partitions.
Use this method for a source type that does not allow key range partitioning such as a flat file source, or when the mapping includes a transformation that does not support key range partitioning. When you enable partitioning based on the number of partitions, you can specify up to 64 partitions.
Consider the number of records to be passed in the mapping to determine an appropriate number of partitions for the mapping. For a small number of records, partitioning might not be advantageous.
If the mapping includes multiple sources, specify the same number of partitions for each source.
You cannot partition a mapping in the following situations:
  • When the mapping uses a parameterized source or source query.
  • When the mapping includes a Web Services or Hierarchy Parser transformation.
  • When the mapping includes multiple sources that use custom relationships or advanced relationships.
When you configure partitions, be sure to save and run the mapping in the Mapping Designer to validate the partition settings.
Some connectors do not support partitioning. For more information about partitioning using a specific connector, see the help for the appropriate connector.


Updated June 30, 2020