Handling default value constraint in SQL Server for Airbyte sync

Summary

Airbyte sync is failing due to default value constraint (‘1970-01-01 00:00:00.000’) in SQL Server causing a ClassCastException error. The source table has correct data for the sync process. What is the fix for this in the Airbyte pipeline?


Question

Hi,

My source table in sql server has default value constraint of (‘1970-01-01 00:00:00.000’) because of this the airbyte sync is failing due to error msg
Caused by: io.debezium.DebeziumException: java.lang.ClassCastException: class java.lang.Long cannot be cast to class java.sql.Timestamp (java.lang.Long is in module java.base of loader 'bootstrap'; java.sql.Timestamp is in module java.sql of loader 'platform')
but this is valid constraint in the source table and data is correct for those tables which needs to flow during the sync process. What is the fix for this in airbyte pipeline?



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.

Join the conversation on Slack

["sql-server", "default-value-constraint", "airbyte-sync", "classcastexception", "fix"]