[COMPASS-4298] JSON-data import causes some data altered Created: 17/May/20 Updated: 29/Oct/23 Resolved: 15/Jun/20 |
|
| Status: | Closed |
| Project: | Compass |
| Component/s: | Compass |
| Affects Version/s: | 1.21.2 |
| Fix Version/s: | 1.22.0 |
| Type: | Bug | Priority: | Critical - P2 |
| Reporter: | Mario Vernari | Assignee: | Alena Khineika |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | JSON, import | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Environment: |
Windows 10 |
||
| Attachments: |
|
||||||||||||||||
| Issue Links: |
|
||||||||||||||||
| Sprint: | Iteration Elderberry | ||||||||||||||||
| Description |
|
JSON-data import mistakes data type and value for many records. The import process ended successfully: no alert was displayed. As for instance, here is the JSON fragment taken from the file to be imported:
Here is the related entry once the import process has been done:
Note that some of the fields were changed from a valid number to a "true". Not all the records are broken, and not clear what is the reason for a so strange behavior. The JSON file was exported with a MongoDB Compass 1.21.2 on another Windows 10 machine. |