Uploaded image for project: 'Commons CSV'
  1. Commons CSV
  2. CSV-239

Cannot get headers in column order from CSVRecord

    XMLWordPrintableJSON

    Details

    • Type: Improvement
    • Status: Resolved
    • Priority: Minor
    • Resolution: Fixed
    • Affects Version/s: 1.6
    • Fix Version/s: 1.7
    • Component/s: Parser
    • Labels:
      None

      Description

      I have a use case where I read many lines from an arbitrary csv file with a given CSVFormat as List<CSVRecord>, transform that list and then want to write the transformed list to another file. 

      When I specify the format as CSVFormat.DEFAULT.withFirstRecordAsHeader() the headers from the first line are available in the CSVRecord object via the CSVRecord.toMap object but their column positions are not (the iteration of the returned map does not reflect column order). Consequently I cannot write a header line in the correct order to the output csv file (which I do when the first CSVRecord is to be written).

      Another option would be to be to ensure that the CSVPrinter object writes the header on the first call to CSVPrinter.printRecord but we should also be able to cover the user case where we are writing to a non-csv format and we still want to write the headers in the correct order. 

      My preference at minimum is that the headers with column order are available from CSVRecord (after all the data to supply this is already present in CVSRecord). The addition of a method `getHeaders` returning a `List<String>` would do the job. I'm happy to submit a PR if desired.

      I've marked this as of minor importance but I think it's a pretty important flaw in the library at the moment that prevents event the simplest of round-trip (read then write) scenarios when the headers are read from the file rather than known up-front.

        Attachments

          Activity

            People

            • Assignee:
              Unassigned
              Reporter:
              davidmoten2 Dave Moten
            • Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved:

                Time Tracking

                Estimated:
                Original Estimate - Not Specified
                Not Specified
                Remaining:
                Remaining Estimate - 0h
                0h
                Logged:
                Time Spent - 3.5h
                3.5h