Affects Version/s: 2.2.0
Fix Version/s: None
Same behavior on Debian and MS Windows (8.1) system. JRE 1.8
It seems that doing counts after filtering for the parser-created columnNameOfCorruptRecord and doing a count afterwards does not recognize any invalid row that was put to this special column.
Filtering for members of the actualSchema works fine and yields correct counts.
Input CSV example:
validCount is 3
Invalid Count is 1
validCount is 4
Invalid Count is 0
Caching the csv after load solves the problem and shows the correct counts.