I have dataset with only one column and number of rows. Why I'm getting different result for tUniqueRow and tAggregateRow ?
Solved! Go to Solution.
may be because - one is count Unique rows and other any rows? :-)
in other words - You have duplicates in this filtered column
But the input to both the components is same and mainly has only one column, and yes this one column is having duplicate values in it. How can the result be different ?
I think tUniqueRow is using fuzzy match for uniqueness, and so the no. of rows are lesser by 33 than that of tAggregateRow.
Thanks for the reply @vapukov.
I guess, what are You mean
if You have only single column and group by this column, it must be same result
because not - need redirect flows to files and compare by diff
for make it more easy compare - You can sort column before store to file
what settings You use in both components?
What is the data type of the single column in your schema? How do you have your tAggregateRow component configured?
Oh, I haven't observed that. Thanks for pointing me out @cterenzi.
Now I'm getting same row count. Which one is good to go for - tUniqueRow or tAggregateRow ?
Talend named a Leader.
Kickstart your first data integration and ETL projects.
Watch the recorded webinar!
Part 2 of a series on Context Variables
Learn how to do cool things with Context Variables
Find out how to migrate from one database to another using the Dynamic schema