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

Transformations

Transformations

Generated keys

Generated keys

The Normalizer transformation generates key values for normalized data.
Generated keys fields appear on the
Normalized Fields
tab when you configure the field to have more than one occurrence.
The
mapping
task generates the following fields for normalized data.
Generated Key
A key value that the task generates each time it processes an incoming row. When a task runs, it starts the generated key with one and increments by one for each processed row.
The Normalizer transformation uses one generated key field for all data to be normalized.
The naming convention for the Normalizer generated key is GK_<redefined_field_name>.
The generated key is not applicable in advanced mode.
Generated Column ID
A column ID value that represents the instance of the multiple-occurring data. For example, if an Expenses field that includes four occurs, the task uses values 1 through 4 to represent each type of occurring data.
The Normalizer transformation uses a generated column ID for each field configured to occur more than one time.
The naming convention for the Normalizer generated key is GCID_<redefined_field_name>.
An
advanced cluster
processes the generated column ID field as a bigint. The Data Integration Server processes the ID as an integer.

0 COMMENTS

We’d like to hear from you!