Fast sort components has been caught in losing records. Simply out-records count is less than in-count. Ratio is about 0.5% (about 10^6 records processed and about 5000 lost). Circumsances are foreign key violations and graph fail.
It’s very bad for commercial components. Clover version is 3.1.2 x64.
Hi Golomeen,
I tried to reproduce your problem but I didn’t succeed. I tried various sorting keys types, composed keys, data sizes, rows counts, …
Can you please provide me some failing sample of data? Or at least information about data structure, rows count and sorting keys?
Thank you.
Your CloverETL Support team
Jaroslav Kubos