You are not logged in.
It seems to me that the component tAggregateRow doesn't work the same way in the 3.1 and the 3.0 version of T.O.S. :
I have a job who read the lines of a file delimited. I use the tAggregateRow to obtain a list of unique couple of two fields (this part of the job is visible in the picture just below). This Aggregate doesn't count or sum or any other operation, I just use the function "group by" and it worked with TOS 3.0.
Since I use the version 3.1, I had to add an operation if I want to use the tAggregateRow, I can't just use "group by" .
Is their a way to use the "group by" function without an operation, or are we obliged to use it with "group by" AND "operation" ?
Last edited by François (2009-05-14 10:06:41)
Indeed, tAggregateRow has changed since 3.1 to be quicker and memory saver. Yet it is possible that the behavior has changed on this point, I think it shouldn't, please request a new bug/feature on this subject.
Already resolved in 3.1.1 with [Bugtracker, bug 7260, fixed] Since 3.1.0 the tAggregateRow-Component always needs a Operation-Field