warnings with join
Moderators: chulett, rschirm, roy
-
- Premium Member
- Posts: 397
- Joined: Wed Apr 12, 2006 2:28 pm
- Location: Tennesse
warnings with join
Hi All i am running a parallel job whic contain seq file , sort , transformer and join stage ,i am getting this warning with almost all fields
Join_114: When checking operator: Dropping component "EndProcessingDate" because of prior component with same name
can any one please help me on this
Thanks in advance
Join_114: When checking operator: Dropping component "EndProcessingDate" because of prior component with same name
can any one please help me on this
Thanks in advance
hi sam here
-
- Charter Member
- Posts: 199
- Joined: Tue Jan 18, 2005 2:50 am
- Location: India
You have two link going to your Join stage, both the link has "EndProcessingDate" column and this column is not part of "KEY", on which you are joining the two links.
Soln: either you drop the column from either of the two link before the join stage itself or change the name of one of them.
Soln: either you drop the column from either of the two link before the join stage itself or change the name of one of them.
Shantanu Choudhary
-
- Premium Member
- Posts: 397
- Joined: Wed Apr 12, 2006 2:28 pm
- Location: Tennesse
Hi Sam,
Are you sure that you are getting the same warning on "EndProcessingDate" column. Can you explain your job at the transformer stage.
Are you sure that you are getting the same warning on "EndProcessingDate" column. Can you explain your job at the transformer stage.
i dropped those columns but still i am getting those warnings , i am having 2 links from the transformer into the join , i have sort before transformer i am dropping those columns in the output of sort.
-
- Premium Member
- Posts: 397
- Joined: Wed Apr 12, 2006 2:28 pm
- Location: Tennesse
-
- Premium Member
- Posts: 397
- Joined: Wed Apr 12, 2006 2:28 pm
- Location: Tennesse
Hi Sam,
Your job is doing something like this.
Data is extracted from Sequential File sorted at sort stage and passing the columns to the transformer stage(here you have two links),using the Join stage to join the links and target(not mentioned).
From your job, You will get same columns for both the links. Based on some constraints you have splited you input stream into two at the transformer stage. Now you need to rename all the columns for one link and do a join based on your condition then pass the wanted columns to the target.![Question :?:](./images/smilies/icon_question.gif)
Your job is doing something like this.
Data is extracted from Sequential File sorted at sort stage and passing the columns to the transformer stage(here you have two links),using the Join stage to join the links and target(not mentioned).
From your job, You will get same columns for both the links. Based on some constraints you have splited you input stream into two at the transformer stage. Now you need to rename all the columns for one link and do a join based on your condition then pass the wanted columns to the target.
Let me know if I got your job design or not. If yes then above explantion may work elsei am getting exactly the same warning i am taking 2 out put link from transformer each has join keys and required columns which are joined in the next join stage.
![Question :?:](./images/smilies/icon_question.gif)
-
- Premium Member
- Posts: 397
- Joined: Wed Apr 12, 2006 2:28 pm
- Location: Tennesse
-
- Charter Member
- Posts: 199
- Joined: Tue Jan 18, 2005 2:50 am
- Location: India
-
- Participant
- Posts: 7
- Joined: Thu Sep 30, 2004 5:22 am
Re: warnings with join
What is the DS version you are working on ?
-
- Premium Member
- Posts: 397
- Joined: Wed Apr 12, 2006 2:28 pm
- Location: Tennesse
-
- Participant
- Posts: 73
- Joined: Tue May 10, 2005 6:21 pm
- Location: Sydney
If you had the column in the source and if you had renamed or dropped in some intermediate stage, RCP will be culptrit.
Else, since its the sequential file, you can go ahead to chage the column name from the source stage.
Else, since its the sequential file, you can go ahead to chage the column name from the source stage.
Impossible doesn't mean 'it is not possible' actually means... 'NOBODY HAS DONE IT SO FAR'