How to avoid starting of lookup file execution at the beginning of the job

[Anonymous]

Hi,

I am trying to create a job like below.

tFileExcelInput_1--->tFilterRow--->tFileExcelOutput_2--->tUniqueRow--->tMap--->tFileExcelOutput_3--main->tmap

                                                                                                                                   tFileExcelInput2--->lookup-->

tFileExcelOutput_3 is the main and tFileExcelInput2 is lookup file. tFileExcelInput2 is the tFileExcelOutput_2. 

But, when I do lookup, lookup file is executing first which should not happen because it is dependent on the data of tFileExcelOutput_2. 

I changed tMap lookup model as Load at each row, this is working, but taking lot of time for large data. Do we have any other alternative to handle this situation.

Thanks in advance,

Meghana.

[fdenis · Accepted solution]

you cannot read the file you are writing in the same sub-job.
so you can split your job or use file or tHashMap to store temp data.
good luck

[Anonymous]

I have split the job and it is working

Thanks,

Meghana.