You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@commons.apache.org by "Gary D. Gregory (Jira)" <ji...@apache.org> on 2020/01/20 23:41:00 UTC

[jira] [Comment Edited] (CSV-248) CSVRecord is not Serializable

    [ https://issues.apache.org/jira/browse/CSV-248?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17019774#comment-17019774 ] 

Gary D. Gregory edited comment on CSV-248 at 1/20/20 11:40 PM:
---------------------------------------------------------------

[~aherbert]

The record's parser field is now transient. 

 


was (Author: garydgregory):
[~aherbert]

The record's parser field is now transient. Please verify and close.

 

> CSVRecord is not Serializable
> -----------------------------
>
>                 Key: CSV-248
>                 URL: https://issues.apache.org/jira/browse/CSV-248
>             Project: Commons CSV
>          Issue Type: Bug
>    Affects Versions: 1.7
>            Reporter: Alex Herbert
>            Priority: Major
>             Fix For: 1.8
>
>
> CSVRecord is no longer Serializable as it stores the CSVParser and that is not serializable.
> The parser contains a list of all the CSVRecords. So to serialize this would serialize a lot of extra information. The cascade of serialization eventually includes the original BufferedReader used to read the data.
> The parser is required for the header map functionality and the getParser() method. The easy fix is to not support any functionality related to the parser after deserialization. If the header map functionality is to be supported the class can store the header map (easy), or overload the serialization methods to record and load the header map (more effort), or something else.
>  
>  



--
This message was sent by Atlassian Jira
(v8.3.4#803005)