You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently the batched line extraction has the potential to break CSV rows where such a row contains unescaped newline chars.
But this is allowed according to the the RFC 4180 specification. Either the current parser needs to ignore newline markers if they appear within a quoted field (CSV) or a different line extraction needs to be made available.
If CSVs are known NOT to contain newline markers, then the batch extraction as it currently exists can still be used for parsing CSVs via batches
The text was updated successfully, but these errors were encountered:
Currently the batched line extraction has the potential to break CSV rows where such a row contains unescaped newline chars.
But this is allowed according to the the RFC 4180 specification. Either the current parser needs to ignore newline markers if they appear within a quoted field (CSV) or a different line extraction needs to be made available.
If CSVs are known NOT to contain newline markers, then the batch extraction as it currently exists can still be used for parsing CSVs via batches
The text was updated successfully, but these errors were encountered: