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

Advanced properties

Advanced properties

Configure advanced properties to define how the Rank transformation processes data. Configure advanced properties on the
Advanced
tab.
The properties that are available vary based on the mapping mode.
Configure the following properties:
Property
Description
Cache Directory
Directory where
Data Integration
creates the data cache and index cache files. By default,
Data Integration
stores the cache files in the directory entered in the Secure Agent $PMCacheDir property for the Data Integration Server.
If you change the cache directory, verify that the directory exists and contains enough disk space for the cache files.
To increase performance during cache partitioning, enter multiple directories separated by semicolons. Cache partitioning creates a separate cache for each partition that processes the transformation.
Default is $PMCacheDir.
Rank 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.
Rank 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.
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.
Transformation Scope
The method in which
Data Integration
applies the transformation logic to incoming data. Select one of the following values:
  • Transaction. Applies the transformation logic to all rows in a transaction. Choose Transaction when the results of the transformation depend on all rows in the same transaction, but not on rows in other transactions.
  • All Input. Applies the transformation logic to all incoming data. When you choose All Input,
    Data Integration
    drops transaction boundaries. Select All Input when the results of the transformation depend on all rows of data in the source.
Default is All Input.
Case Sensitive String Comparison
Specifies whether
Data Integration
uses case-sensitive string comparisons when it ranks strings. To ignore case in strings, disable this option. Default is enabled.
On an
advanced cluster
, comparisons are always case-sensitive.
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.
Default is enabled.

0 COMMENTS

We’d like to hear from you!