[resolved] Getting rows which not gets updated.

[Anonymous]

Hi All
My CSV File contains
a1;b1;c1
a2;b2;c2
a3;b3;c3
a4;b4;c4
a5;b5;c5
My Db has
a1;NULL;c1
a2;NULL;c2
via this Job
tFileInputDelimeter----row1---->tMysqlOutput(using action Update)
I want a1 and a2 to get updated and a3,a4,a5 rows separately,in a file OR in Memory.
Can anyone help me out in this.
Thanks

[Anonymous · Accepted solution]

hi,
reload at each time is often used when you've got a lot of data in lookup and decide to filter (where clause) to get only part of these.
It's possible as The **GlobalMapKey** field is automatically created when you selected the **Reload at each row** option.

**Reload at each row**: At each row, the lookup
gets loaded again. This is mainly interesting in Jobs where the lookup volume is
large, while the main flow is pretty small. Note that this option allows you to
use dynamic variable settings such as where clause, to change/update the lookup
flow on the fly as it gets loaded, before the main flow join is processed. This
option could be considered as the counter-part of the **Store temp data** option that is available for file
lookups.

with cache :

**Reload at each row (cache)**: Expressions (in
the Lookup table) are assessed and looked up in the cache first. The results of
joins that have already been solved, are stored in the cache, in order to avoid
loading the same results twice. This option optimizes the processing time and
helps improve processing performance of the **tMap** component.

have a look at talend help tMap operation :
https://help.talend.com/search/all?query=tMap+operation&content-lang=en
you also got some great explanation & examples at component references tMap :
https://help.talend.com/search/all?query=tMap&content-lang=en
espacially :
### Scenario 6: Advanced mapping with lookup reload at each row

hope it help
regards
laurent