Summary
User reports an issue with Airbyte deployed on Kubernetes where timestamps with timezone from Postgres are altered during synchronization to Snowflake and Google Sheets, leading to incorrect time representation.
Question
Hello everyone,
I’m encountering an issue with Airbyte deployed on Kubernetes, syncing data from Postgres to Snowflake (and also tested with Google Sheets as an additional destination). My columns in Postgres are of the type “timestamp with timezone”. However, during synchronization, the timezone of the timestamps is altered.
For example:
• In Postgres, I have a timestamp: “2018-10-03 03:05:01.142 +0200”
• In Snowflake, it appears as: “2018-10-03 01:05:01.142 +0000”
This issue also occurs with Google Sheets as a destination. My Kubernetes cluster is set to UTC time, but I am puzzled as to why this would affect the conversion of timezones in this manner, since Airbyte is supposed to preserve the original timezone of the data. This conversion is particularly problematic with regard to daylight saving time changes, making time-sensitive data less reliable.
Has anyone experienced this problem or have any suggestions on how I might resolve it? Any help would be greatly appreciated.
Thank you in advance for your support!
This topic has been created from a Slack thread to give it more visibility.
It will be on Read-Only mode here. Click here if you want
to access the original thread.