We've recently moved to CloverETL Designer 3.3.0.063M1 from CloverETL Designer 2.9.1 and I've noticed different behavior in the UniversalDataReader components.
With the older version if I specify "Number of Skipped Records = 1" and "Max Number of Records = 100" then the first record (header) would be skipped and the next 100 records would be read. Using the same property settings on the newer version only 99 records are read after skipping the first. So the max records count appears to include the skipped records.
It seems that the new behavior is wrong or am I missing something?
With the older version if I specify "Number of Skipped Records = 1" and "Max Number of Records = 100" then the first record (header) would be skipped and the next 100 records would be read. Using the same property settings on the newer version only 99 records are read after skipping the first. So the max records count appears to include the skipped records.
It seems that the new behavior is wrong or am I missing something?
-
Hi, CodeMonkee,
I tried to reproduce your issue but everything works fine on my side, behavior of UDR was not changed. Can you post some sample graph and input file which does not work on your side? However, to be sure, I can only recommend you to use our latest 3.3.1 final version instead of milestone version M1.
Best regards,
Please sign in to leave a comment.
Comments 1