regarding aggregator stage
Moderators: chulett, rschirm, roy
-
- Participant
- Posts: 228
- Joined: Tue Oct 03, 2006 7:08 pm
regarding aggregator stage
hi gurus,
my design is ODBC---->AGGREGATOR----->ODBC----->JOB1
i want to make use of aggregator o/p and give it as i/p to job2 .
using aggregator stage iam calculating sum(sal).
iam bulding up another job in which i want to add extra column called sum(sal) (ie) i want to make use of o/p from job1.
instead of continuing the same job, iam designing another job.
ODBC---->TRANSFORMER---->ODBC---->JOB2
can anyone help me in design.
cheers;
vijay
my design is ODBC---->AGGREGATOR----->ODBC----->JOB1
i want to make use of aggregator o/p and give it as i/p to job2 .
using aggregator stage iam calculating sum(sal).
iam bulding up another job in which i want to add extra column called sum(sal) (ie) i want to make use of o/p from job1.
instead of continuing the same job, iam designing another job.
ODBC---->TRANSFORMER---->ODBC---->JOB2
can anyone help me in design.
cheers;
vijay
Is there any reason why you want to break this up into two jobs?
You could do it in one job.
Bu if you have to, what is stopping you from doing it?
Job1
Job2
The Target of your first job will the Source for your second job.
You could do it in one job.
Bu if you have to, what is stopping you from doing it?
Job1
Code: Select all
ODBC---->AGGREGATOR----->ODBC
Code: Select all
ODBC---->TRANSFORMER---->ODBC
Narasimha Kade
Finding answers is simple, all you need to do is come up with the correct questions.
Finding answers is simple, all you need to do is come up with the correct questions.
-
- Charter Member
- Posts: 822
- Joined: Sat Sep 17, 2005 5:25 pm
- Location: USA
-
- Premium Member
- Posts: 1255
- Joined: Wed Feb 02, 2005 11:54 am
- Location: United States of America
Instead of this !!!
Hi gurus,
My design is
I want to make use of aggregator o/p and give it as i/p to job2 .
Using aggregator stage iam calculating sum(sal).
I am bulding up another job in which I want to add extra column called sum(sal) i.e., I want to make use of the o/p from job1.
Instead of continuing the same job, I am designing another job.
Can anyone help me in design?
cheers;
Vijay.
How about putting it this way?vijaykumar wrote:hi gurus,
my design is ODBC---->AGGREGATOR----->ODBC----->JOB1
i want to make use of aggregator o/p and give it as i/p to job2 .
using aggregator stage iam calculating sum(sal).
iam bulding up another job in which i want to add extra column called sum(sal) (ie) i want to make use of o/p from job1.
instead of continuing the same job, iam designing another job.
ODBC---->TRANSFORMER---->ODBC---->JOB2
can anyone help me in design.
cheers;
vijay
Hi gurus,
My design is
Code: Select all
ODBC---->AGGREGATOR----->ODBC----->JOB1
Using aggregator stage iam calculating sum(sal).
I am bulding up another job in which I want to add extra column called sum(sal) i.e., I want to make use of the o/p from job1.
Instead of continuing the same job, I am designing another job.
Code: Select all
ODBC---->TRANSFORMER---->ODBC---->JOB2
cheers;
Vijay.
Anything that won't sell, I don't want to invent. Its sale is proof of utility, and utility is success.
Author: Thomas A. Edison 1847-1931, American Inventor, Entrepreneur, Founder of GE
Author: Thomas A. Edison 1847-1931, American Inventor, Entrepreneur, Founder of GE
-
- Charter Member
- Posts: 822
- Joined: Sat Sep 17, 2005 5:25 pm
- Location: USA
-
- Premium Member
- Posts: 1255
- Joined: Wed Feb 02, 2005 11:54 am
- Location: United States of America
Well! In trying to conserve space, the result is that the OP's messages/statements are difficult to decipher. And in turn, we all will reply a ton of times in order to get the gist of the question, thereby losing much more space. So, if the question is well framed in the first place, then there will be the right amount of replies, thereby conserving much more space.us1aslam1us wrote:Whale,
He seems to be in a hurry to solve this!! (Or might be trying not to consume much space on the dsxchange server )But definitely that will help the person reading that.
Sam
Whale.
Anything that won't sell, I don't want to invent. Its sale is proof of utility, and utility is success.
Author: Thomas A. Edison 1847-1931, American Inventor, Entrepreneur, Founder of GE
Author: Thomas A. Edison 1847-1931, American Inventor, Entrepreneur, Founder of GE
-
- Charter Member
- Posts: 822
- Joined: Sat Sep 17, 2005 5:25 pm
- Location: USA
I still dont get the exact question. In job1 a Aggregator been used and Sum(Sal) is calculated. In next job (Job2) the output of Job1 is used. What is the need to add a new column. If the output is aggregated, the sum(sal) will be available as one of the field.
Or if you want to add sum(sal) for certain group, you desing is justified.
And btw, what is the clarification that you need in the job design?
Or if you want to add sum(sal) for certain group, you desing is justified.
And btw, what is the clarification that you need in the job design?
Impossible doesn't mean 'it is not possible' actually means... 'NOBODY HAS DONE IT SO FAR'
-
- Premium Member
- Posts: 1255
- Joined: Wed Feb 02, 2005 11:54 am
- Location: United States of America
Thanks!narasimha wrote:Whale,
Nice that you handled the case too, I always wanted to mention it, but you did it
Right! and especially,
Code: Select all
'I' <> 'i'
Anything that won't sell, I don't want to invent. Its sale is proof of utility, and utility is success.
Author: Thomas A. Edison 1847-1931, American Inventor, Entrepreneur, Founder of GE
Author: Thomas A. Edison 1847-1931, American Inventor, Entrepreneur, Founder of GE