[pg-source] Fix timestamp precision issue with debezium #52617
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
octavia-squidington-iii
added
area/connectors
burakku
force-pushed
the
pg-ts-precision-fix-6857
branch
from
d3f8a1e to
3967934
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
What
This PR is trying to fix the issue in https://github.com/airbytehq/oncall/issues/6857, which the timestamp data converter in pg connector use different precision for different length ts and it cause precision inconsistency with debezium
How
I changed the precision to microsecond consistently for all ts that have precision less than microsecond
Review guide
User Impact
All ts have less precision than microsecond will be converted to microsecond for postgres source connector
Can this PR be safely reverted and rolled back?