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.

Sign up for GitHub

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

Jump to bottom

Postgres CDC source should not lose milliseconds precision when a timestamp/datetime is converted to string #12026

Closed
grishick opened this issue Apr 14, 2022 · 0 comments · Fixed by #14534
Closed

Postgres CDC source should not lose milliseconds precision when a timestamp/datetime is converted to string #12026

grishick opened this issue Apr 14, 2022 · 0 comments · Fixed by #14534
Assignees
@yurii-bidiuk
Labels
area/connectors Connector related issues connectors/source/postgres type/bug Something isn't working

Comments

@grishick
Copy link
Contributor

This is a followup to #9157

Exit criteria:

  • acceptance test that verifies that we are carrying over millisecond precision in Postgres CDC connector during initial sync of a table configured for incremental syncs
  • acceptance test for subsequent incremental sync

Size estimate: medium (2-3 days)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@yurii-bidiuk yurii-bidiuk

Labels
area/connectors Connector related issues connectors/source/postgres type/bug Something isn't working
Projects
None yet
Milestone
No milestone
3 participants
@bleonard @grishick @yurii-bidiuk