[ 
https://issues.apache.org/jira/browse/CSV-147?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Benedikt Ritter updated CSV-147:
--------------------------------
    Description: 
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.

  was:
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:

public String[] getLastRecordData() {
  return this.record.toArray(new String[this.record.size()]);
}

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.


> 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
>   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)

Reply via email to