-
Type: Investigation
-
Resolution: Won't Do
-
Priority: Major - P3
-
Affects Version/s: None
-
Component/s: Import/Export
-
None
-
Not Needed
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.
- is caused by
-
COMPASS-4163 Imported large CSV file into Compass creates document count mismatch
- Closed