Skip to content
New issue

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

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

Already on GitHub? Sign in to your account

_ts property is being set to local time despite using IncludeMetadataFields flag #139

Open
JohnDStrasz opened this issue Aug 1, 2024 · 0 comments

Comments

@JohnDStrasz
Copy link

JohnDStrasz commented Aug 1, 2024

We have an issue whereby the _ts timestamp field is not being restored from the source in the destination. The _ts property is being populated with the latest epoch time.

We're copying from our Cosmos account in the cloud to our local Emulator for local development needs.

The migrationsettings file is below and we are using the IncludeMetadataFields flag on both the export and import (not sure if it's needed on both). For certain business purposes, we would like the _ts to be preserved.

Is there a way to achieve what we need?

{
"Source": "cosmos-nosql",
"SourceSettings": {
"Query": "SELECT * FROM c",
"IncludeMetadataFields": true
},
"Destination": "cosmos-nosql",
"DestinationSettings": {
"WriteMode": "Upsert",
"IncludeMetadataFields": true
},
"Operations": [
{
"SourceSettings": {
"ConnectionString": "AccountEndpoint=xxx",
"Database": "xxx-dev",
"Container": "MyContainer"
},
"DestinationSettings": {
"ConnectionString": "xxx",
"Database": "xxx-local",
"Container": "MyContainer",
"PartitionKeyPath": "/myPartitionKey"
}
}
]
}

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant