[COMPASS-4198] Support headerless .csv imports Created: 09/Mar/20  Updated: 14/Feb/23  Resolved: 12/Jan/23

Status: Closed
Project: Compass
Component/s: Import/Export
Affects Version/s: None
Fix Version/s: No version

Type: Investigation Priority: Major - P3
Reporter: Lucas Hrabovsky (Inactive) Assignee: Unassigned
Resolution: Won't Do Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Attachments: PNG File Screenshot 2020-03-09 12.55.13.png    
Issue Links:
Problem/Incident
is caused by COMPASS-4163 Imported large CSV file into Compass ... Closed
Epic Link: COMPASS-5576
Documentation Changes: Not Needed

 Description   

From COMPASS-4163

You can see this problem manifest immediately via the preview table:

And while we are able to insert all 4+Gb the resulting collection is not usable unless we create a view or use aggregation pipeline to $project the correct field names. (see this comment for detailed working example: https://jira.mongodb.org/browse/COMPASS-4163?focusedCommentId=2954991&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-2954991)

A smaller sample of the dataset: (12Mb) part 1 of the yearly data as a CSV file (part 1) (CSV, 12.6MB)

We can control supplying headers/field names for the parser. If we add a checkbox like "[x] Includes Headers" we could name the fields like field_1, field_2 etc. automatically. Field names could also be renamable via the preview header rows.



 Comments   
Comment by Le Roux Bodenstein [ 12/Jan/23 ]

Our designs don't allow for headerless imports. We use the header to work out the field names and have no plans to allow filling in field names manually.

Generated at Wed Feb 07 22:35:33 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.