Failed to Connect MYSQL (Verification error(s) occurred for CHECK)

  • Is this your first time deploying Airbyte?: Yes
  • OS Version / Instance: Ubuntu
  • Memory / Disk: you can use something like 4Gb
  • Deployment: Docker
  • Airbyte Version: 0.40.22
  • Source name/version: MYSQL/1.0.13
  • Destination name/version: Redshift/ 0.3.15
  • Step: The issue is happening during sync
The connection tests failed.
Verification error(s) occurred for CHECK. Errors: [$.replication_method: should be valid to one and only one of schema, but more than one are valid: {"title":"Standard","description":"Standard replication requires no setup on the DB side but will not be able to represent deletions incrementally.","required":["method"],"properties":{"method":{"type":"string","const":"STANDARD","order":0}}}{"title":"Logical Replication (CDC)","description":"CDC uses the Binlog to detect inserts, updates, and deletes. This needs to be configured on the source database itself.","required":["method"],"properties":{"method":{"type":"string","const":"CDC","order":0},"initial_waiting_seconds":{"type":"integer","title":"Initial Waiting Time in Seconds (Advanced)","description":"The amount of time the connector will wait when it launches to determine if there is new data to sync or not. Defaults to 300 seconds. Valid range: 120 seconds to 1200 seconds. Read about <a href=\"\">initial waiting time</a>.","default":300,"min":120,"max":1200,"order":1},"server_time_zone":{"type":"string","title":"Configured server timezone for the MySQL source (Advanced)","description":"Enter the configured MySQL server timezone. This should only be done if the configured timezone in your MySQL instance does not conform to IANNA standard.","order":2}}}, $.replication_method: string found, object expected]

Save changes and test

1 Like

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

Facing the same issue. Can someone assist?

Hello sundari, it’s been a while without an update from us. Are you still having problems or did you find a solution?