Page 1 of 1

Aggregator Stage

Posted: Wed Apr 09, 2008 1:08 pm
by syam.neelam
Could anyone explain in detail about the disadvantages of using Aggregator Stage.

Posted: Wed Apr 09, 2008 3:24 pm
by ray.wurlod
I am not aware of any.

Posted: Wed Apr 09, 2008 10:37 pm
by BugFree
disadvantages of using Aggregator Stage? here you go:

1) It takes up space on your designer canvas.
2) You will have to sort the data before you use aggregator stage. Again space on the canvas.
3) When running it takes up valuable CPU time, resource/scratch space.
4) And aborts all the time on the last record, so you will have to rerun the job again.

Hell I am not creative enough. This is the best i could do. :(

Posted: Thu Apr 10, 2008 12:00 am
by ray.wurlod
1) ho hum
2) not true - you can use hash table method or allow tsort operators to be inserted
3) doesn't everything?
4) my glass is half full - no, wait a minute, that's not my glass, my glass had MORE in it than that

Posted: Sun Oct 17, 2010 12:02 am
by agpt
Hi Ray,

I was just trying to look into aggregator stage scenario I came across and found this post here in the history. Is it true that aggregator stage aborts on last record every time? I don't think so as I have seen running it fine too. May be I am missing something from the statement made above. Could you please clarify it to me. Is there any other disadvantage from this stage apart from resource consumption?

Posted: Sun Oct 17, 2010 7:27 am
by chulett
About all you are missing from BugFree's comments is the irony they are dripping with. Perhaps some sarcasm as well. :wink: