[Sources-MySQL] MySQL TINYINT(1) CDC sync produces “invalid number value false” error when syncing to Redshift

[duongdr]

I am using Airbyte version 2.0.1 with the following setup:

• Source: MySQL
• Destination: Redshift
• Source settings: JDBC URL Params: tinyInt1isBit=false
• Update Method: Read Changes using Change Data Capture (CDC)

During the initial full load, MySQL columns with type TINYINT(1) were synced successfully, and the destination column type in Redshift was correctly created as INT, which is the expected behavior.

However, during subsequent CDC sync runs, Airbyte throws the following error:
source ERROR main i.a.c.AirbyteConnectorRunnable(run):38 Failed class io.airbyte.cdk.read.ReadOperation operation execution. java.lang.IllegalArgumentException: invalid number value false at io.airbyte.cdk.data.ShortCodec.decode(JsonCodec.kt:133) ~[bulk-cdk-core-base-0.1.77.jar:?] at io.airbyte.cdk.data.ShortCodec.decode(JsonCodec.kt:128) ~[bulk-cdk-core-base-0.1.77.jar:?] at io.airbyte.integrations.source.mysql.MySqlSourceDebeziumOperations.deserializeRecord-0vE2DaM(MySqlSourceDebeziumOperations.kt:141) ~[io.airbyte.airbyte-integrations.connectors-source-mysql.jar:?] at io.airbyte.cdk.read.cdc.CdcPartitionReader$EventConsumer.emitRecord(CdcPartitionReader.kt:324) ~[bulk-cdk-toolkit-extract-cdc-0.1.77.jar:?]

It seems that during CDC events, Debezium still interprets TINYINT(1) as a boolean, causing values like false to appear instead of 0 or 1, even though tinyInt1isBit=false is set. The destination then fails because it expects a numeric value.

Expected Behavior

I want Airbyte to always preserve MySQL TINYINT(1) values exactly as 0 or 1, both in full load and CDC sync, without converting them to boolean.

Question

What configuration or workaround should I use to ensure that MySQL TINYINT(1) values are treated strictly as integers during CDC sync, so the destination continues receiving 0 and 1 instead of true/false?

[Cris Navas (CrisNavasM)]

Hey, same issue here any workaround?

@octavia-bot devin-ai-integration Matt Bayley (@mwbayley)

Were you able to solve it, duongdr ?

[duongdr]

If your destination is the same as mine (Redshift), I haven’t been able to find any workaround for this issue yet. You might try creating a view on the destination as a possible workaround Cris Navas (@CrisNavasM)

[Muhammad Usman Iftikhar (musmanir)]

I have another Azure destination and still getting the same problem. What I understood it is a problem with CDC. and Airbyte is working on this: #76187. I am not sure how much time will it take to resolve.

[Matt Bayley (mwbayley)]

We're in the process of releasing version 3.52.0 of source-mysql. In this version you'll see a new option at the bottom of the source configuration page under the Optional fields to "Treat TINYINT(1) Columns as Integers". The default continues to be to treat these columns as Boolean, but this configuration allows you to change that to Integer. Note that the JDBC URL Params should not contain tinyInt1isBit. Happy syncing!