T) Explain the Run time Behaviour of Reformat Component ?

-

The Reformat component processes your data records through these steps:

Basic Setup:

  • Each output port is numbered (out0, out1, out2, etc.)

  • Each output has matching reject and error ports (reject0/error0, reject1/error1, etc.)

Step-by-Step Process:

  1. Read a Record

    • Takes one record from the input port

  2. Check Selection Filter (if you have one)

    • If the filter expression returns FALSE: Record is skipped, go to next record

    • If the filter returns NULL: Graph stops with an error message

    • If the filter returns TRUE (or no filter exists): Continue processing

  3. Determine Where to Send the Record

    • If you have only one output port: Record goes to that port automatically

    • If you have multiple output ports:

      • Uses output-index to decide which port(s) get this record

      • Can send to one port or multiple ports

      • If there's an error choosing ports, record goes to reject0

  4. Transform the Record

    • For each designated output port:

      • If no transform is defined: Uses automatic field mapping

      • If transform is defined: Runs your custom logic

    • Ports are processed in order (out0 first, then out1, etc.)

  5. Handle Results

    • If transform succeeds: Record goes to the output port

    • If transform fails or returns NULL:

      • Error message goes to error port

      • Original record goes to reject port

    • If too many rejects occur: Graph stops running

  6. Repeat

    • Moves to the next input record and starts over

Key Points:

  • Records can be sent to multiple output ports

  • Each transform runs independently

  • Unconnected reject/error ports automatically discard records

  • The order of port processing matters for functions like next_in_sequence

This process continues until all input records are processed or the graph stops due to errors/reject limits.

 

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