CSVParser should give more details when it errors out
Description
It's pretty tough to debug the CSVParser if you have more than one in a single pipeline. It would be nice to log the record it failed on so you can debug easier. Also, it's pretty rare to switch back and forth between input fields and parsed fields when running through the plugin. Seems like when that happens it's usually the result of a bad field name or something.
Also, we should check for index out of bounds error and throw a better message.
Release Notes
None
Activity
Show:
NitinM June 9, 2020 at 1:40 AM
Closing jiras older than 2+ years of not being updated.
Won't Fix
Pinned fields
Click on the next to a field label to start pinning.
It's pretty tough to debug the CSVParser if you have more than one in a single pipeline. It would be nice to log the record it failed on so you can debug easier. Also, it's pretty rare to switch back and forth between input fields and parsed fields when running through the plugin. Seems like when that happens it's usually the result of a bad field name or something.
Also, we should check for index out of bounds error and throw a better message.