Incorrect Time format (UTC) used for CDC MSSQL Sync

Connector Questions & Issues
1

Hi,

I’m getting incorrect time format (UTC) for _airbyte_emitted_at, _ab_cdc_updated_at, _airbyte_start_at, _airbyte_end_at.
_airbyte_normalized_at is OK (Brussels Time).
This is causing problems (data not updated) when doing a sync after an update performed on my Source Table.
I’m using CDC Incremental Deduped+History.
Source & Destination are MSSQL.
How can I get Brussels Time for all those Airbyte’s Technical Columns ?
Thanks.
Best regards,
Eric

2

Hello there! You are receiving this message because none of your fellow community members has stepped in to respond to your topic post. (If you are a community member and you are reading this response, feel free to jump in if you have the answer!) As a result, the Community Assistance Team has been made aware of this topic and will be investigating and responding as quickly as possible.
Some important considerations that will help your to get your issue solved faster:

  • It is best to use our topic creation template; if you haven’t yet, we recommend posting a followup with the requested information. With that information the team will be able to more quickly search for similar issues with connectors and the platform and troubleshoot more quickly your specific question or problem.
  • Make sure to upload the complete log file; a common investigation roadblock is that sometimes the error for the issue happens well before the problem is surfaced to the user, and so having the tail of the log is less useful than having the whole log to scan through.
  • Be as descriptive and specific as possible; when investigating it is extremely valuable to know what steps were taken to encounter the issue, what version of connector / platform / Java / Python / docker / k8s was used, etc. The more context supplied, the quicker the investigation can start on your topic and the faster we can drive towards an answer.
  • We in the Community Assistance Team are glad you’ve made yourself part of our community, and we’ll do our best to answer your questions and resolve the problems as quickly as possible. Expect to hear from a specific team member as soon as possible.

Thank you for your time and attention.
Best,
The Community Assistance Team

3

Hi,

I’m using MSSQL Source 0.4.28 & MSSQL Destination 0.1.22.
The issue I’m facing is that the _airbyte_emitted_at, _ab_cdc_updated_at, _airbyte_start_at & _airbyte_end_at are UTC time.
_airbyte_normalized_at is OK (Brussels Time).
This is, I suppose, causing problems (data not updated) when doing a sync after an update performed on my Source Table.
Any idea how to have Brussels Time used for all those Airbyte Technical Columns ?

Best regards,
Eric

4

I’m using Airbyte 0.40.32.
Snapshot Isolation Level set.
CDC Incremental Deduped + History.
First Sync is working.
Sync after update is NOT OK.
Rows are in corresponding raw table but not correct in corresponding scd table + last version of the row marked as Inactive.

5

Hi, I got almost the same problem as you did.
I built Airbyte on GKE via helm, using chart 0.45.8, also, data are synced from SQL Server to BigQuery via CDC incremental Deduped + History.
Have you tried modifying timezone for all pods? Refer to the following URL to configure global timezone, It is working for me.

6

https://github.com/airbytehq/airbyte/issues/25237