[COMPASS-6158] commas followed by spaces confuse date field CSV imports Created: 26/Sep/22  Updated: 15/Mar/23  Resolved: 15/Mar/23

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

Type: Task Priority: Major - P3
Reporter: Le Roux Bodenstein Assignee: Unassigned
Resolution: Won't Fix Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
depends on COMPASS-6422 listCSVFields() import function & tests Closed
depends on COMPASS-6423 analyzeCSVFields() import function an... Closed
depends on COMPASS-6425 importCSV() import function and tests Closed
depends on COMPASS-6519 Switch to using importCSV() Closed
depends on COMPASS-6520 Switch to using importJSON() Closed
Epic Link: COMPASS-5576
Documentation Changes: Not Needed

 Description   

See
https://www.mongodb.com/community/forums/t/unable-to-import-csv-file-to-time-series-collection-using-compass/189428

I think we should either be resilient and consistently work with comma-space separeted fields OR we should warn or error. Right now it is weird in that we split the fields for the preview which makes it look like it will work but then later some parsing or code deeper down (ie. the code that eventually tries to turn this into a date) doesn't support the space being there.

There might be more cases of this bug.


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