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 This error occurs due to a type mismatch during MySQL CDC ingestion when processing spatial/geometry data (such as

POINT

or

GEOMETRY

columns). What is Happening 1. Debezium's Representation: When reading MySQL CDC change events via Debezium, spatial/geometric fields are often emitted as a structured JSON object containing spatial components, such as

{"x": ..., "y": ..., "wkb": ..., "srid": ...}

[PostGIS geometry/geography columns NULL on CDC path]. 2. Bulk CDK Binary Codec Failure: The connector's schema mapping or deserializer is attempting to decode this field using Airbyte's binary codec (

BinaryCodec

). Airbyte's binary decoder strictly expects a JSON binary node (a base64-encoded binary string) and throws this exact error when it encounters an object structure instead:if (!encoded.isBinary) { throw IllegalArgumentException("invalid binary value $encoded") }[JsonCodec.kt] Because the emitted event is a JSON object map (

{"x": ..., "y": ..., "wkb": ...}

) rather than a valid binary node, decoding fails with

java.lang.IllegalArgumentException: invalid binary value ...

. Potential Workarounds and Solutions 1. Switch to Standard Sync (Non-CDC): If real-time change data capture is not strictly required, switch the sync mode from CDC to Scan Changes with User Defined Cursor (Standard replication). JDBC snapshot/standard reads typically handle spatial/binary type mappings differently and avoid this Debezium CDC serialization path [CDC fails on MySQL 8.4 tagged GTIDs]. 2. Deselect the Geometry Column: If you do not strictly need the spatial/geometry column in your destination, edit the connection catalog in the Airbyte UI and uncheck the specific column causing the issue. 3. Check for Connector Updates: Ensure you are on the latest release of

source-mysql

. Similar CDC type handling and spatial converter issues have been patched across database connectors (such as the addition of custom spatial converters or adjustments to Debezium converters) [PostGIS geometry/geography columns NULL on CDC path]. 👍 0 button 👎 0 button ℹ️ Tip: Mention @kapa.ai in the thread for follow-ups or DM the app for 1-to-1 help.