Table of Contents

Search

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

Transformations

Transformations

Dynamic Lookup example

Dynamic Lookup example

To configure a Lookup transformation to be dynamic, use a dynamic lookup cache.
A dynamic cache is helpful when the source table contains a large amount of data or it contains duplicate primary keys.
The following example illustrates the advantage of using a dynamic cache rather than a static cache when the source table includes duplicate primary keys.
You want to update your payroll table with data from your Human Resources department. The payroll table includes the following data, where ID is the primary key:
ID
Name
Location
1
Abhi
USA
2
Alice
UK
You create a mapping with a Lookup transformation and use the payroll table for the target and the lookup cache. You configure the cache to be dynamic because you expect the Human Resources department's table to contain duplicate keys.
In the mapping, you specify the Human Resources department's table to be the source. The source table includes the following data:
ID
Name
Location
1
Abhi
India
2
Alice
UK
3
James
Japan
3
James
USA
You create a
mapping
task to update the payroll table. When the
mapping
task begins, it creates the cache file that contains the rows in the target table. As the task processes the rows, it flags the first row as an update and it updates the cache. It flags the third row as an insert and inserts the row in the cache. It flags the fourth row as an update because the row exists in the cache.
If you follow the same scenario using a static cache, the task flags the fourth row as an insert. The cache does not contain the row for James because it does not update as the task processes the rows. The target database produces an error because it cannot handle two rows with the same primary key.

0 COMMENTS

We’d like to hear from you!