Open Snamnik opened 5 months ago
have found the issue. it's due to a section of the code in MongoDataSinkExtension Class, BuildDynamicObjectTree() where 'id' will be added rather than '_id' for MongoDB sink.
I see BuildDynamicObjectTree() is a general behavior which has been using in many places of the repo. but can we handle this issue for MongoDB as a configuration, just before adding the object to the Bson Document?
if you agree with the above suggestion, then I can make a PR to apply this logic. @bowencode @codingbandit
I'm going to migrate my data from cosmos-nosql to mongodb . the tool doesn't map the cosmos id field to mongodb _id field. for example: cosmos data:
the mapped data in mongo
how can I resolve this issue?