Warning from source: invalid binary value {"x":31.6238861,"y":30.4578677,"wkb":"AQEAAADS7dv/tp8/QA5lTdE2dT5A","srid":null} See less invalid binary value {"x":31.6238861,"y":30.4578677,"wkb":"AQEAAADS7dv/tp8/QA5lTdE2dT5A","srid":null} java.lang.IllegalArgumentException: invalid binary value {"x":31.6238861,"y":30.4578677,"wkb":"AQEAAADS7dv/tp8/QA5lTdE2dT5A","srid":null} I get this error anyone can help me I enabled cdc on mysql when ingesting data this error occur

Thinking completed I'm sorry, but the provided knowledge sources do not explicitly address a direct fix or dedicated setting for this specific MySQL spatial/geometry binary parsing error. However, based on the codebase structure in the knowledge sources, here is what is causing this issue and potential ways to handle it: Root Cause This error occurs when Airbyte processes a MySQL spatial/geometry column (such as

POINT

,

POLYGON

, or

GEOMETRY

) during Change Data Capture (CDC): 1. Debezium representation: When Debezium reads MySQL spatial/geometry data from the binlog, it outputs an object structure representing coordinates and the Well-Known Binary (WKB) payload, for example:{"x": 31.6238861, "y": 30.4578677, "wkb": "AQEAAADS7dv/tp8/QA5lTdE2dT5A", "srid": null} 2. Type mismatch in Airbyte CDK: Airbyte maps the column or underlying type to a binary type requiring binary decoding (

BinaryCodec

).

BinaryCodec

validates that the incoming node is binary (

encoded.isBinary

), and throwsjava.lang.IllegalArgumentException invalid binary value valuewhen an object/JSON node is passed instead of raw binary bytes [JsonCodec.kt]. Workarounds and Next Steps The provided documentation does not contain an explicit configuration toggle for MySQL geometry types during CDC. To mitigate or work around the issue: 1. Deselect the Geometry/Spatial Columns: If you do not strictly require the spatial/geometry column in your destination, open the connection settings in the Airbyte UI and uncheck the affected column from the stream catalog schema. 2. Switch Replication Method: If continuous CDC binlog reading is not strictly required for that table, switch the sync mode from CDC to standard incremental or full refresh. Non-CDC snapshot paths query MySQL directly over JDBC, which handles certain spatial data types differently than Debezium's binlog reader [Github Issue (closed)]. 3. Use a Generated/View Column in MySQL: If you need the coordinates or geometry in your destination, create a database view or a generated column that converts the spatial value into a string representation (e.g., using

ST_AsText(geom)

or

ST_AsGeoJSON(geom)

), and sync that column instead. 4. Report or Check for Updates: Ensure you are using the latest version of

source-mysql

. If the error persists, consider filing an issue on the Airbyte GitHub repository with your MySQL version, connector version, and the table schema so the connector team can register a custom converter for Debezium's geometry structures. 👍 0 button 👎 0 button ℹ️ Tip: Mention @kapa.ai in the thread for follow-ups or DM the app for 1-to-1 help.

this solution doesnot align with me

Try #C01AHCD885S