Uploaded image for project: 'Compass '
  1. Compass
  2. COMPASS-3581

Messes up large numbers, when importing or inserting documents

    XMLWordPrintable

Details

    • Bug
    • Status: Closed
    • Critical - P2
    • Resolution: Fixed
    • 1.17.0-beta.5
    • 1.22.0
    • None
    • Ubuntu 16.04 (compass), Firefox 66.0.3 (Cloud)
    • Iteration Dingo, Iteration Elderberry, Iteration Fig

    Description

      I think I found quite an important bug concerning large int64 numbers in mongoDB.

      When I import json documents with large numbers, the numbers change*!*

      For example, I have a file with the field, id: 964982886377099271, when I import the file with `Collection; Import Data; Json` this changes to id:964982886377099264. 
      This example file is in the attachment. It also happens with other numbers of similar size.

      The same also happens, when I press the `Insert Document` button inside of Compass.
      I try to create an entry with id: 964982886377099271(Int64) and after I enter 96498288637709927 it changes to 96498288637709920 and then I enter 1 and it changes to 964982886377099264.

      The same also applies, when I press the `Insert Document` button on cloud.mongodb.com.

      I tried to find issues regarding the same topic, but could not find any. This bug is quite tremendous, when you insert some documents containing large numbers to mongodb and afterwards you use the numbers inside an application for some processing, the numbers you used in the processing could be wrong and therefore your processing is incorrect as well.

       

      Best regards,
      Jannis

       

       

      Attachments

        Issue Links

          Activity

            People

              irina.shestak@mongodb.com Irina Shestak (Inactive)
              jannisbush Jannis Rautenstrauch
              Votes:
              0 Vote for this issue
              Watchers:
              10 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: