Table of Contents

Search

  1. Preface
  2. Introduction to Transformations
  3. Transformation Ports
  4. Transformation Caches
  5. Address Validator Transformation
  6. Aggregator Transformation
  7. Association Transformation
  8. Bad Record Exception Transformation
  9. Case Converter Transformation
  10. Classifier Transformation
  11. Comparison Transformation
  12. Consolidation Transformation
  13. Data Masking Transformation
  14. Data Processor Transformation
  15. Decision Transformation
  16. Duplicate Record Exception Transformation
  17. Expression Transformation
  18. Filter Transformation
  19. Hierarchical to Relational Transformation
  20. Java Transformation
  21. Java Transformation API Reference
  22. Java Expressions
  23. Joiner Transformation
  24. Key Generator Transformation
  25. Labeler Transformation
  26. Lookup Transformation
  27. Lookup Caches
  28. Dynamic Lookup Cache
  29. Match Transformation
  30. Match Transformations in Field Analysis
  31. Match Transformations in Identity Analysis
  32. Normalizer Transformation
  33. Merge Transformation
  34. Parser Transformation
  35. Python Transformation
  36. Rank Transformation
  37. Read Transformation
  38. Relational to Hierarchical Transformation
  39. REST Web Service Consumer Transformation
  40. Router Transformation
  41. Sequence Generator Transformation
  42. Sorter Transformation
  43. SQL Transformation
  44. Standardizer Transformation
  45. Union Transformation
  46. Update Strategy Transformation
  47. Web Service Consumer Transformation
  48. Parsing Web Service SOAP Messages
  49. Generating Web Service SOAP Messages
  50. Weighted Average Transformation
  51. Window Transformation
  52. Write Transformation
  53. Appendix A: Transformation Delimiters

Developer Transformation Guide

Developer Transformation Guide

Persistent Lookup Cache

Persistent Lookup Cache

A persistent lookup cache is a cache that the Integration Service reuses for multiple runs of the same mapping. Use a persistent lookup cache when the lookup source does not change between mapping runs.
By default, the Integration Service uses a non-persistent cache when you enable lookup caching in a Lookup transformation. The Integration Service deletes the cache files when the mapping completes. The next time you run the mapping, the Integration Service builds the memory cache from the lookup source.
If you configure the Lookup transformation to use a persistent lookup cache, the Integration Service saves and reuses cache files for multiple runs of the mapping. A persistent cache eliminates the time required to read the lookup table and rebuild the lookup cache.
The first time the Integration Service runs a mapping with a persistent lookup cache, the Integration Service saves the cache files to disk. The next time the Integration Service runs the mapping, it builds the memory cache from the cache files.
You can configure the Integration Service to rebuild a persistent lookup cache if the original lookup source changes. When you rebuild a cache, the Integration Service creates new cache files and writes a message to the Integration Service log.

0 COMMENTS

We’d like to hear from you!