Data & Analytics
Airbyte MySQL can turn long text into silent NULLs
Audit raw and final tables when Airbyte MySQL typing converts strings longer than 512 characters.
November 11, 2026
A green sync is not proof that every value survived typing. An Airbyte MySQL destination issue reports strings longer than 512 characters present in the raw table but NULL in the final table on destination-mysql 1.1.2. The issue traces the path to JSON_VALUE without an explicit return type. MySQL’s manual says that call defaults to VARCHAR(512) and NULL ON ERROR.
Find the boundary, not just the missing value
Select a representative long-text column and compare the same record IDs in the source, Airbyte raw table and typed final table. Count rows whose raw value exceeds 512 characters and whose final value is NULL. Keep missing source values separate from conversion failures. The issue’s reported row count belongs to that installation; use your own count for incident scope.
Check connector version, MySQL version and destination sync mode. Do not assume every MySQL destination release has this behavior. Capture a small reproducible row and the generated typing SQL before changing production tables. The connector issue is still a report, not a universal statement about every deployment.
Repair with reconciliation
If the pattern is confirmed, decide whether to hold the affected stream, patch or upgrade the connector, or use a controlled transformation path that preserves long strings. Test the candidate fix against values just below and above the boundary. Backfill affected records, then compare checksums or lengths from raw to final for a sample and add a recurring quality check for new rows.
Adovo’s view
Data loss that keeps the job green is more dangerous than a visible failure. Treat raw-to-final conversion as a contract with measurable invariants. The job status tells you whether work ran; reconciliation tells you whether the customer record survived.
