You are not logged in.
Announcement
Unanswered posts
|
- Index
- » Usage, Operation
- » [resolved] tAggregateSortedRow missing a row compared to tAggregateRow
Post a reply
Topic review (newest first)
- pcoffre
- 2012-02-13 11:55:02
Great, thanks for the feedback.
Best,
Pcoffre.
- bcastell
- 2012-02-13 11:07:39
The error was that i has set the input row count to 10000000 (a high limit I thought I'd never reach).
I've set it now to 1 and it works fine and fast.
- pcoffre
- 2012-01-05 11:27:55
Hi,
You will need to add it to "Talend DI".
Best,
Pcoffre.
- bcastell
- 2012-01-04 18:06:41
ok
which project am I supposed to add it to ? I can't find one that concern TOS.
Thanks
- JohnGarrettMartin
- 2012-01-04 17:21:15
that sounds like a component bug to me. You can issue a bug in the bugtracker and get updates on when it is fixed:
http://jira.talendforge.org/secure/Dashboard.jspa
- bcastell
- 2012-01-04 16:20:08
Hi,
I had a job using a tAggregateRow that failed because of memory space. I found out that I could use the tAggregateSortedRow instead and not only my memory
problem was solved but it even ran quicker. The trouble is the output is not the same and a row is missing in the new job.
I have put and ran the 2 jobs together to show the problem. There is 1 line difference in the output as shown in the image. The input file is the same, so are the other
component other than the tSortRow, whose set up is also in the picture.
The pictures were made from a simplified example of the real job. None the less the error is the same. Whether I use a delimited file or a tMSSqlInput as source,
I get the same problem and it consistently occurs on the last record (of the table or the file).
Has someone seen this before, has an idea for why it happens ?
I'm using TOS 4.2.2 on Win2008 64bits
Thanks