T) Broadcast versus Replicate component. Anyone could u plz explain ?

-



  • Broadcast and replicate behavior varies with flow type and default flow type is different for both. It's always difficult to remember it unless you try all scenarios. On a short note when you connect this component between same depth, default flow type for broadcast is all to all and it multiplies the data.
  •  I would suggest to read help and simultaneously run trials. Primary motive of broadcast is data parallelism and it duplicates data in each partition flow. As I said it behaves differently based on flow type and you need to run it to get correct understanding.

Comments

Post a Comment

Popular posts from this blog

T) For data parallelism, we can use partition components. For component parallelism, we can use replicate component. Like this which component(s) can we use for pipeline parallelism?

-
You can use components that does not require any sorted data (explicit or in memory sort) to get pipeline parallelism. Like Reformat,FBE, Redefine components. And Components that needed sorted data like join, roll-up, merge, sort, partition by key and sort breaks the pipeline parallelism.  
Read more

T) When to use sort within groups ?

-
Use Sort within Groups only if records within a group are processed before being sorted on a minor key. i.e. if processing "A" needs records to be sorted on field {"1"} and later in the flow processing "B" needs records to be sorted on field {"1", "2"}. In this case before processing "2" and after processing "1" use sort within groups with major-key as {"1"} and minor key as {"2"}. If records are not grouped to start with, use Sort with a multi-part key. There is no benefit to using Sort within Groups directly after using a Sort component.
Read more

T) Explain about on .abi-unc files in abinitio ?

-
 These are temporary files used by the checkout process. Under normal circumstances you should not see them. However, if the checkout failed or was interrupted, these files can be left behind. Delete them and try checking out again.    Details: The checkout procedure includes two steps to ensure that a checkout does not leave your sandbox in a half-checked-out state: 1. It checks out the files, but gives them the .abi-unc suffix (for "uncommitted"). 2. Once every file is successfully checked out, the . abi-unc files replace the real files. If an error occurs midway through checkout, any .abi-unc files that have been created might be left behind. If you receive the error message "Cannot write project parameters file: /path/filename.abi-unc" during checkout and you see . abi-unc files, delete them and try checking out again. Uncommitted files are usually left behind because a checkout process was aborted.  
Read more