Sparse Lookup - Dropping component because of prior componen
Moderators: chulett, rschirm, roy
-
- Participant
- Posts: 43
- Joined: Wed Feb 12, 2014 12:34 pm
- Location: Hyderabad, India
Sparse Lookup - Dropping component because of prior componen
I'm doing a sparse lookup on oracle table on Key but when I'm running job I'm getting error as Dropping component Key because of prior component with same name Key. Actually the column for which it is saying it is dropping due to same name is lookup key only and usually we get this error for other joins when non joining columns are with same name but here for key joining column it is giving this error. Could you please advise, thanks.
SyedMuhammadMehdi
Basically the problem is that the sparse lookup is returning the key to the output link, and the source link is also sending the key to the output link. So it complains about it.
Easiest solution is to use custom SQL in the sparse lookup that doesn't return the key column value. Even though it is on the list of columns (because it was sent to the sparse lookup), it doesn't have to be returned as a value.
Easiest solution is to use custom SQL in the sparse lookup that doesn't return the key column value. Even though it is on the list of columns (because it was sent to the sparse lookup), it doesn't have to be returned as a value.