[
https://issues.apache.org/jira/browse/CSV-164?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15020652#comment-15020652
]
Romain Manni-Bucau commented on CSV-164:
----------------------------------------
Well I tend to agree it is a bad case but my point is it is common enough to be
supported - jsefa, beanio support it btw.
An example is top 10 extraction "inline" where you can get something like next
sample without much control in $$ softwares:
Top1;Score;Top2;Score;Top3;Score....
Said otherwise i d prefer to not assume in [csv] the design is well done but
would be nicer for end users to be flexible.
Code to support it is not much and would be better to concentrate all csv code
in a single project @asf than in multiple.
Does it make sense?
> support duplicate headers
> -------------------------
>
> Key: CSV-164
> URL: https://issues.apache.org/jira/browse/CSV-164
> Project: Commons CSV
> Issue Type: Bug
> Reporter: Romain Manni-Bucau
>
> nothing prevents a CSV to have the same time the same header name so
> validation at the end of org.apache.commons.csv.CSVFormat#validate should
> likely disappear or should support a flag to disable it
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
