Skip to content
New issue

Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? # to your account

CosmosDB to CosmosDB doesn't migrate "Id" field #100

Closed
vacuum-in opened this issue Dec 12, 2023 · 3 comments · Fixed by #116
Closed

CosmosDB to CosmosDB doesn't migrate "Id" field #100

vacuum-in opened this issue Dec 12, 2023 · 3 comments · Fixed by #116

Comments

@vacuum-in
Copy link

At the source database we have two fields "Id" and "id" where "id" is the CosmosDB standard field. Only standard field is created at sink container.
Source container:

{
    "Id": "f703df15-32fa-4788-d7cd-08dbf7edaaaa",
.....
    "id": "f703df15-32fa-4788-d7cd-08dbf7edaaaa"
}

Sink container:

{
.....
    "id": "f703df15-32fa-4788-d7cd-08dbf7edaaaa"
...
}

"IncludeMetadataFields" set to true

@sebas-ambrero
Copy link

@vacuum-in I had the same issue with dmt-2.1.4-win-x64.

Checked out the code, and ran it locally, that worked fine for me.

@adambarath
Copy link
Contributor

Any update on this?

adambarath added a commit to adambarath/data-migration-desktop-tool that referenced this issue Mar 18, 2024
bowencode added a commit that referenced this issue Mar 29, 2024
Fix for issue: CosmosDB to CosmosDB doesn't migrate "Id" field #100
@bowencode
Copy link
Collaborator

Using the latest code, the PreserveMixedCaseIds sink setting will now update this behavior to include multiple cases of id fields.

# for free to join this conversation on GitHub. Already have an account? # to comment
Labels
None yet
Projects
None yet
4 participants