[COMPASS-5127] Messes up large number when inserting documents Created: 29/Sep/21  Updated: 03/Oct/23

Status: Open
Project: Compass
Component/s: Documents, UI / UX
Affects Version/s: 1.28.4
Fix Version/s: None

Type: Bug Priority: Major - P3
Reporter: Philip Linkewitz Assignee: Unassigned
Resolution: Unresolved Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

Edition Windows 10 Pro
Version 21H1
Installed at ‎16.‎09.‎2020
system build 19043.1237
Windows Feature Experience Pack 120.2212.3530.0


Attachments: JPEG File inserting-2.jpg     JPEG File result-1.jpg     JPEG File types.jpg    
Issue Links:
Related
related to COMPASS-3581 Messes up large numbers, when importi... Closed
related to COMPASS-3806 Inserting or updating int64 data type... Closed
Story Points: 2

 Description   

Problem Statement/Rationale

Compass changes big numbers (17+ digits) when inserting. When editing a created document, the specified type is a double.

Example:

1443218867782705158 → 1443218867782705200

 

 

Steps to Reproduce

  1. select ADD DATA
  2. select Insert Document
  3. Insert Document with a large int64 (1443218867782705158). Any key can be used

Expected Results

Compass should insert an Int64 with the exact value

Actual Results

Compass changes the last couple of digits

Additional Notes

I also have a collection where I cannot find a document with Compass by looking for an ID with such a value, but it is there, and I can find it with drivers.

Could not reproduce in any other collection.



 Comments   
Comment by Jessica Sigafoos [ 14/Feb/22 ]

pl.lkw.01@gmail.com, following up on this. Do you see this same issue when you enter it as extended JSON?

Comment by Jessica Sigafoos [ 25/Jan/22 ]

pl.lkw.01@gmail.com, following up on this.  Do you see this same issue when you enter it as extended JSON?

Comment by Jessica Sigafoos [ 01/Dec/21 ]

pl.lkw.01@gmail.com do you see this same issue when you enter it as extended JSON?

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