Azure / azure-documentdb-datamigrationtool

Azure DocumentDB Data Migration Tool
MIT License
387 stars 183 forks source link

Numbers are getting altered during the migration #123

Closed Joncn89 closed 2 years ago

Joncn89 commented 4 years ago

We used the Migration-Tool to migrate data to a new collection using a different partition key. What we found is that the documents were not exactly the same after the migration.

We were able to reproduce the issue with a very simple document:

{
    "testProperty": 2100.607537417505,
    "id": "01f2d29b-7f5d-49fd-99e4-832ad86989e7",
    "_rid": "5KARAKqcl2iChB4AAAAAAA==",
    "_self": "dbs/5KARAA==/colls/5KARAKqcl2g=/docs/5KARAKqcl2iChB4AAAAAAA==/",
    "_etag": "\"0d00b160-0000-0d00-0000-5f58cc990000\"",
    "_attachments": "attachments/",
    "_ts": 1599655065
}

Both collections, the source and the target, were completely fresh so they were the newest version. We used version 1.8.3 of the Migration Tool.

After the migration the content of the migrated document was now:

{
    "testProperty": 2100.6075374175052,
    "id": "01f2d29b-7f5d-49fd-99e4-832ad86989e7",
    "_rid": "5KARAIb+p3+ChB4AAAAAAA==",
    "_self": "dbs/5KARAA==/colls/5KARAIb+p38=/docs/5KARAIb+p3+ChB4AAAAAAA==/",
    "_etag": "\"2d00f993-0000-0d00-0000-5f58ccb80000\"",
    "_attachments": "attachments/",
    "_ts": 1599655096
}

so as you can see the value of the property testProperty changed from 2100.607537417505 to 2100.6075374175052.

We also tried to export it to a JSON-File and also in that JSON-File the number was already altered.

[
  {
    "testProperty": 2100.6075374175052,
    "id": "01f2d29b-7f5d-49fd-99e4-832ad86989e7"
  }
]