Versions Compared
Version | Old Version 9 | New Version 10 |
---|---|---|
Changes made by | ||
Saved on |
Key
- This line was added.
- This line was removed.
- Formatting was changed.
Insert excerpt | ||||||||
---|---|---|---|---|---|---|---|---|
|
Scenario
Combining a large stream table with data from a small streamtable, where values in the small stream table will only used once in the result. For each pair of matching records from the data sets, a single record is produced in the output.
Example
You have a stream table containing all attendees of an upcoming football match and a small stream table of people who are banned from attending matches.
Solution
In the below screenshot, 'Source Stream stream 1' about 2000 records and we want to enrich this data with data from 'Source Stream stream 2', which contains about 50 records.
- The result
- table type is set to 'Calculate'.
- The pipe from 'Source
- table 1' is a pull pipe with no grouping.
- The pipe from 'Source
- table 2' is a lookup pipe. A filter should be added to define the joining key between the 2
- tables
- All
- table attributes use the attribute name, prefixed by the pipe name. For example, in1.Attribute1.
Image RemovedImage Added
You need to make sure that all attributes that you refer to with _out prefixes in the joining key have a lower order number than those that use the lookup pipe prefix.
For example, in the above screenshot, it is essential that Attribute1 has a lower order number than Attribute3. If the order of the attributes were switched around, Attribute3 would not return a value, because the filter would be looking for records where Attribute1 is null, because it would not yet be calculated.
Info |
---|
Watch out for the multiple records returned by your lookup pipe. You will either need to:
|
For more information on lookup pipes see Data Properties.