You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@commons.apache.org by "Rick Oosterholt (Jira)" <ji...@apache.org> on 2021/10/05 12:51:00 UTC
[jira] [Commented] (CSV-147) Better error handling in CSV, see
included code
[ https://issues.apache.org/jira/browse/CSV-147?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17424457#comment-17424457 ]
Rick Oosterholt commented on CSV-147:
-------------------------------------
Is there any news on this?
> Better error handling in CSV, see included code
> -----------------------------------------------
>
> Key: CSV-147
> URL: https://issues.apache.org/jira/browse/CSV-147
> Project: Commons CSV
> Issue Type: Improvement
> Components: Parser
> Affects Versions: 1.1
> Reporter: Steven Peterson
> Priority: Major
> Labels: easyfix
> Fix For: Discussion
>
> Attachments: csv-exceptionsupport.patch
>
> Original Estimate: 0.25h
> Remaining Estimate: 0.25h
>
> When parsing long files, and there is problem with parsing the data, it would be very useful to know the exact data that is bad when an exception is thrown. As CSVParser maintains a portion of the current record that was read when an exception is thrown (in the 'record' property), can we make this information public through something like this:
> {code:java}
> public String[] getLastRecordData() {
> return this.record.toArray(new String[this.record.size()]);
> }
> {code}
> With a method like this, it would be easy to pull in part of the data that was in the faulty record after an exception was thrown, aiding in cleaning up the data.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)