[
https://issues.apache.org/jira/browse/CSV-302?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17622238#comment-17622238
]
Gary D. Gregory edited comment on CSV-302 at 10/21/22 12:52 PM:
----------------------------------------------------------------
Let's forget about serialization, it will be dropped in 2.0 and we do not
support it from version to version, it's been broken many times in the past.
See discussion https://lists.apache.org/thread/p017hp6qq1zcphg7pr1ko4swvvw8ynch
was (Author: garydgregory):
Let's forget about serialization, it will be dropped in 2.0 and we do not
support it from version to version, it's been broken many times in the past.
> CSVFormat.duplicateHeaderMode requires default for backward compatibility
> -------------------------------------------------------------------------
>
> Key: CSV-302
> URL: https://issues.apache.org/jira/browse/CSV-302
> Project: Commons CSV
> Issue Type: Bug
> Components: Parser
> Affects Versions: 1.x
> Reporter: Markus Spann
> Priority: Minor
> Time Spent: 2.5h
> Remaining Estimate: 0h
>
> The member in class {{CSVFormat}}
> {code:java}
> boolean allowDuplicateHeaderNames{code}
> was recently replaced by
> {code:java}
> DuplicateHeaderMode duplicateHeaderMode{code}
> The boolean defaults to {{{}false{}}}, while the member of type
> {{DuplicateHeaderMode}} defaults to {{{}null{}}}.
> {{duplicateHeaderMode}} must be initialized with {{DISALLOW}} for backward
> compatibility.
> The change is also problematic with regards to serialization. The class is
> serializable and {{serialVersionUID}} is unchanged between versions. The
> boolean setting {{allowDuplicateHeaderNames}} in an object serialized in
> version 1.9.0 or earlier would always be de-serialized to
> {{duplicateHeaderMode = null}} in the current head.
> To handle the code changes correctly, customized de-serialization would need
> to be implemented.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
