[
https://issues.apache.org/jira/browse/CSV-147?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14275744#comment-14275744
]
Benedikt Ritter commented on CSV-147:
-------------------------------------
Hello [~speterson],
I've spent some time to look into this and now I'm not sure I understand the
issue. The record is only created at the end of parsing a full CSV record . If
the reader that is used to parse the content throws an exception from it's read
method while we're in the middle of reading the record, there won't be any
content in the record. The only thing we can do is preserve a copy of the last
record that has been read completely.
regards,
Benedikt
> 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
> Labels: easyfix
> Fix For: Discussion
>
> 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
(v6.3.4#6332)
