What are the limitations of joiner transformation?
When the integration service processes an unsorted joiner transformation, it reads all master rows before it reads the detail rows. To ensure it reads all master rows before the detail rows, the integration service blocks all the details source while it caches rows from the master source. As it blocks the detail source, the unsorted joiner is called a blocking transformation.
Regards,
Hari Babu
- You cannot use a joiner transformation when input pipeline contains an update strategy transformation.
- You cannot use a joiner if you connect a sequence generator transformation directly before the joiner.
What are the different types of joins?
- Normal join: In a normal join, the integration service discards all the rows from the master and detail source that do not match the join condition.
- Master outer join: A master outer join keeps all the rows of data from the detail source and the matching rows from the master source. It discards the unmatched rows from the master source.
- Detail outer join: A detail outer join keeps all the rows of data from the master source and the matching rows from the detail source. It discards the unmatched rows from the detail source.
- Full outer join: A full outer join keeps all rows of data from both the master and detail rows
What is joiner cache?
When the integration service processes a joiner transformation, it reads the rows from master source and builds the index and data cached. Then the integration service reads the detail source and performs the join. In case of sorted joiner, the integration service reads both sources (master and detail) concurrently and builds the cache based on the master rows.
When the integration service processes a joiner transformation, it reads the rows from master source and builds the index and data cached. Then the integration service reads the detail source and performs the join. In case of sorted joiner, the integration service reads both sources (master and detail) concurrently and builds the cache based on the master rows.
Why joiner is a blocking transformation?
When the integration service processes an unsorted joiner transformation, it reads all master rows before it reads the detail rows. To ensure it reads all master rows before the detail rows, the integration service blocks all the details source while it caches rows from the master source. As it blocks the detail source, the unsorted joiner is called a blocking transformation.
Regards,
Hari Babu
I feel Informatica is the best and most useful aspect of providing solutions to some very complex and useful IT resources and even problems.
ReplyDeleteInformatica Read Soap API