Avoiding Multiple Lookup

Post questions here relative to DataStage Enterprise/PX Edition for such areas as Parallel job design, Parallel datasets, BuildOps, Wrappers, etc.

Moderators: chulett, rschirm, roy

Post Reply
ashishm
Premium Member
Premium Member
Posts: 37
Joined: Thu Jun 16, 2011 8:12 am
Location: india

Avoiding Multiple Lookup

Post by ashishm »

Hi , I am running a job which requires me to do multiple lookups on the same table for each record.
I know in Informatica i could do an unconnected Lookup and call it for each column..Being new to DS environ still trying to figure out a better way.

The situation I am talking about is

ColumnA ColumnB ColumnC ColumnD ColumnE
1 A B C D


ANd Lookup Table is

ColumnA ColumnB
A XXX
B YYY
c ZZZ
D MMM

and the output I want is

1 XXX YYY ZZZ MMM

I dont want to do a Join as I may loose records using the JOin Stage.

Please suggest a better way to do it.
chulett
Charter Member
Charter Member
Posts: 43085
Joined: Tue Nov 12, 2002 4:34 pm
Location: Denver, CO

Post by chulett »

Does this need to be a PX job? There's an equivalent to the unconnected lookup on the Server side, hence the question. Not saying there isn't a PX answer to this, but nothing is popping into my head at the moment other than the Server solution.

Out of curiousity, what 8.x version do you have?
-craig

"You can never have too many knives" -- Logan Nine Fingers
ashishm
Premium Member
Premium Member
Posts: 37
Joined: Thu Jun 16, 2011 8:12 am
Location: india

Post by ashishm »

I am using version 8.1 with fix pack 2.. and yes it has to be a PX JOb,Client does not wants too many Server Job..
chulett
Charter Member
Charter Member
Posts: 43085
Joined: Tue Nov 12, 2002 4:34 pm
Location: Denver, CO

Post by chulett »

How many is "too many"? Should be the right tool for the right job.

Was wondering if the looping functionality in the 8.5 release might be leveraged for something like this but it's academic, it would seem.
-craig

"You can never have too many knives" -- Logan Nine Fingers
ray.wurlod
Participant
Posts: 54607
Joined: Wed Oct 23, 2002 10:52 pm
Location: Sydney, Australia
Contact:

Post by ray.wurlod »

Use a Lookup stage with four reference inputs, all linking to the same reference data set.
IBM Software Services Group
Any contribution to this forum is my own opinion and does not necessarily reflect any position that IBM may hold.
chulett
Charter Member
Charter Member
Posts: 43085
Joined: Tue Nov 12, 2002 4:34 pm
Location: Denver, CO

Post by chulett »

Does that leverage a single cache under the covers, or four?
-craig

"You can never have too many knives" -- Logan Nine Fingers
ray.wurlod
Participant
Posts: 54607
Joined: Wed Oct 23, 2002 10:52 pm
Location: Sydney, Australia
Contact:

Post by ray.wurlod »

Four.
IBM Software Services Group
Any contribution to this forum is my own opinion and does not necessarily reflect any position that IBM may hold.
prakashdasika
Premium Member
Premium Member
Posts: 72
Joined: Mon Jul 06, 2009 9:34 pm
Location: Sydney

Re: Avoiding Multiple Lookup

Post by prakashdasika »

ashishm wrote:I dont want to do a Join as I may loose records using the JOin Stage.

Please suggest a better way to do it.
Why do you lose records by using a Join Stage? Please Explain.
Prakash Dasika
ETL Consultant
Sydney
Australia
chulett
Charter Member
Charter Member
Posts: 43085
Joined: Tue Nov 12, 2002 4:34 pm
Location: Denver, CO

Post by chulett »

ray.wurlod wrote:Four.
OK. That's what I thought... which means it doesn't really emulate the Informatica unconnected lookup but is akin to a 'connected' one, or rather four connected ones.
-craig

"You can never have too many knives" -- Logan Nine Fingers
Post Reply