DSXchange

hi,

I am having the below data in my source sequential file: i need to remove duplicates only using transformer stage My target sequential file should contain below data: Please help me to achieve this.
The job is whether server or parallel doesn't matter.
But i need to use only transformer for removing duplicates.


Thanks

Server job with a hashed file that just stores the key or record number or whatever uniquely identifies a record. Do a lookup to the hashed file and if the key does not exist, write it to the hashed file and pass it out the output link. If you get a hit on the hashed file, do nothing, as in do not pass the record through nor update the hashed file.

Note that either the hashed file must not be cached or the cache must be "locked for updates". I prefer the former approach. Also note that the write to the hashed file must be in the same transformer that does the lookup to ensure the locks (if you take that approach) are handled appropriately.

Thanks craig!
is there any way to achieve the same using parallel job?

thanks

pandeesh wrote:But i need to use only transformer for removing duplicates.

Why?

Just I would like to know whether it's possible .

Server job is easy there no special work from our side, whereas in PX you need to sort it, use stages like remove dup, TFM etc.

DS User

pandeesh wrote:Just I would like to know whether it's possible .

The answer to that is "yes". But why?

The philosophy of parallel jobs is basically one task, one stage type. That's why there are so many more stage types than server jobs have.

I'm assuming this would be complicated on the PX side by the (apparent) need to retain the original input order... which leads me to think the dreaded "fork join" design would be appropriate in that case. Somehow.

Not at all. Set up a stable, unique sort on the input link to the Transformer stage and map the columns across the stage.

hi
for parallel you can use the stage variables
var1=link1
var2=if var1 = var3 then 1 else 0
var3= link1

In either version you can use stage variables... as long as the input is sorted in a usable fashion.