This blog discusses simplification of even the most complicated data integration challenges. When we can achieve that, and make data processing more efficent, it's the best of both worlds. The new cache mechanism is a benefit to both of those goals.
SaveInputRecord : stores an input row to back of the cache GetInputRecord : retrieves a saved row from the front of the cache
Here are few scenarios discussed by Tony in detail where using a cache will prove VERY helpful:
- The input data set is sorted by fund id and valuation date in ascending order. We have an unknown number of records for each fund. The requirement is to output the five most recent valuations for any fund and if there are not at least five, do not output any.
There is a varying number of clients (N) related to each salesperson. The requirement is to label each such client detail record with a label that reads "1 of N".
- An input file contains multiple bank accounts for each customer.
The requirement is to show the percentage of the total balance for each individual account record. Perhaps one or more of these sounds familiar to you. You may also refer to the Information Server InfoCenter for more detail on this solution.