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

[6.0.1] Cosmos: Use configured serializer when reading #26702

Merged
merged 1 commit into from
Nov 16, 2021

Conversation

AndriySvyryd
Copy link
Member

Fixes #26690

Description

When converting JSON values to DateTime we are using the default serializer that converts UTC times to local. However in #25741 we changed the serializer options used for saving the values, causing them to no longer round-trip.

Customer impact

The queried DateTime values are now in local time. Depending on the app logic this can result in data corruption.

How found

Customer reported on 6.0

Regression

Yes, this worked in 5.0

Testing

Added test for this scenario.

Risk

Low, the change just make sure to use the existing serializer consistently. Also added a quirk mode.

@AndriySvyryd AndriySvyryd requested a review from a team November 16, 2021 02:12
@AndriySvyryd AndriySvyryd added this to the 6.0.x milestone Nov 16, 2021
@AndriySvyryd AndriySvyryd changed the title Cosmos: Use configured serializer when reading [6.0.x] Cosmos: Use configured serializer when reading Nov 16, 2021
@AndriySvyryd AndriySvyryd modified the milestones: 6.0.x, 6.0.1 Nov 16, 2021
@AndriySvyryd AndriySvyryd merged commit 6fc3e17 into release/6.0 Nov 16, 2021
@AndriySvyryd AndriySvyryd deleted the Issue26690 branch November 16, 2021 04:28
@ajcvickers ajcvickers removed this from the 6.0.1 milestone Nov 17, 2021
@ajcvickers ajcvickers changed the title [6.0.x] Cosmos: Use configured serializer when reading [6.0.1] Cosmos: Use configured serializer when reading Nov 17, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants