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. Data Services transformation
  9. Deduplicate transformation
  10. Expression transformation
  11. Filter transformation
  12. Hierarchy Builder transformation
  13. Hierarchy Parser transformation
  14. Hierarchy Processor transformation
  15. Input transformation
  16. Java transformation
  17. Java transformation API reference
  18. Joiner transformation
  19. Labeler transformation
  20. Lookup transformation
  21. Machine Learning transformation
  22. Mapplet transformation
  23. Normalizer transformation
  24. Output transformation
  25. Parse transformation
  26. Python transformation
  27. Rank transformation
  28. Router transformation
  29. Rule Specification transformation
  30. Sequence Generator transformation
  31. Sorter transformation
  32. SQL transformation
  33. Structure Parser transformation
  34. Transaction Control transformation
  35. Union transformation
  36. Velocity transformation
  37. Verifier transformation
  38. Web Services transformation

Transformations

Transformations

Advanced properties

Advanced properties

You can configure advanced properties for a Joiner transformation. The advanced properties control settings such as the tracing level for session log messages, cache settings, null ordering, and whether the transformation is optional or required.
You can configure the following properties:
Property
Description
Tracing Level
Detail level of error and status messages that
Data Integration
writes in the session log. You can choose terse, normal, verbose initialization, or verbose data. Default is normal.
Cache Directory
Specifies the directory used to cache master or detail rows and the index to these rows.
By default,
Data Integration
uses the directory entered in the Secure Agent $PMCacheDir property for the Data Integration Server. If you enter a new directory, make sure that the directory exists and contains enough disk space for the cache files. The directory can be on a mapped or mounted drive.
Null Ordering in Master
Null ordering in the master pipeline. Select Null is Highest Value or Null is Lowest Value.
Null Ordering in Detail
Null ordering in the detail pipeline. Select Null is Highest Value or Null is Lowest Value.
Data Cache Size
Data cache size for the transformation. Select one of the following options:
  • Auto.
    Data Integration
    sets the cache size automatically. If you select Auto, you can also configure a maximum amount of memory for
    Data Integration
    to allocate to the cache.
  • Value. Enter the cache size in bytes.
Default is Auto.
Index Cache Size
Index cache size for the transformation. Select one of the following options:
  • Auto.
    Data Integration
    sets the cache size automatically. If you select Auto, you can also configure a maximum amount of memory for
    Data Integration
    to allocate to the cache.
  • Value. Enter the cache size in bytes.
Default is Auto.
Sorted Input
Specifies that data is sorted. Select this option to join sorted data, which can improve performance.
Master Sort Order
Specifies the sort order of the master source data. Select Ascending if the master source data is in ascending order. If you select Ascending, enable sorted input. Default is Auto.
Transformation Scope
Specifies how
Data Integration
applies the transformation logic to incoming data:
  • Transaction. Applies the transformation logic to all rows in a transaction. Choose Transaction when a row of data depends on all rows in the same transaction, but does not depend on rows in other transactions.
  • All Input. Applies the transformation logic on all incoming data. When you choose All Input,
    Data Integration
    drops incoming transaction boundaries. Choose All Input when a row of data depends on all rows in the source.
  • Row. Applies the transformation logic to one row of data at-a-time. Choose Row when a row of data does not depend on any other row.
Optional
Determines whether the transformation is optional. If a transformation is optional and there are no incoming fields, the
mapping
task can run and the data can go through another branch in the data flow. If a transformation is required and there are no incoming fields, the task fails.
For example, you configure a parameter for the source connection. In one branch of the data flow, you add a transformation with a field rule so that only Date/Time data enters the transformation, and you specify that the transformation is optional. When you configure the
mapping
task, you select a source that does not have Date/Time data. The
mapping
task ignores the branch with the optional transformation, and the data flow continues through another branch of the mapping.

0 COMMENTS

We’d like to hear from you!
Koki Watanabe - November 12, 2023

Why Sorted Input can improve performance?

Informatica Documentation Team - November 13, 2023

Hi Koki Watanabe, Thanks so much for reaching out! This is explained in the following topic in the Data Integration Performance Tuning Guide: Optimizing joiner transformations

When you configure the Joiner transformation to use sorted data, Data Integration improves performance by minimizing disk input and output. You'll see the greatest performance improvement when you work with large data sets. For an unsorted Joiner transformation, designate the source with fewer rows as the master source.