MySQL 1.0.1 (GA) Source Normalization Failure

  • Is this your first time deploying Airbyte?: No
  • OS Version / Instance: Ubuntu
  • Memory / Disk: 48gb
  • Deployment: Docker
  • Airbyte Version: 0.40.1
  • Source name/version: MySQL 1.0.1
  • Destination name/version: Snowflake 0.38
  • Step: Normalization Failure
	  100038 (22018): Numeric value 'true' is not recognized,externalMessage=Normalization failed during the dbt run. This may indicate a problem with the data itself.,metadata=io.airbyte.config.Metadata@33b335ee[additionalProperties={attemptNumber=2, jobId=46501, from_trace_message=true}],stacktrace=4 of 6 ERROR creating incremental model MY_SCHEMA.MY_TABLE......................................................... [ERROR in 13.78s]

Sync was passing before I upgraded from source-mysql:0.6.12 to source-mysql:1.0.1

schema of failed table, which hasn’t change pre and post updating the source connector:

_ab_cdc_deleted_at: String
_ab_cdc_log_file: String
_ab_cdc_log_pos: Number
_ab_cdc_updated_at: String
<MY_COLUMNS>: Boolean
<MY_COLUMNS>: Number
<MY_COLUMNS>: Number
<MY_COLUMNS>: Number
<MY_COLUMNS>: Number

Related Updating Schema via API doesn't persist

It seems as if the mysql source is inferring the columns incorrectly from the source i.e. tinyint(1) is being cast to numeric. in the source DB it is 1/0 and in snowflake it is true/false in the _AIRBYTE_RAW_TABLE but is trying to be cast to numeric

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.
The Community Assistance Team

Perhaps caused by this ?

that looks promising. although I actually think this could be an issue with the destination (snowflake) and incorrect casting in the normalisation phase

Daniel can you check Edward’s comment in Github?

Im posting a new issue here with the latest specs and logs attached