Skip to content

Add MySQL FAQ entry for unsupported MariaDB partial row events #6487

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
Blargian merged 3 commits into from
Jul 3, 2026
Merged

Add MySQL FAQ entry for unsupported MariaDB partial row events #6487

Changes from all commits
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
24515cb
Add MySQL FAQ entry for unsupported MariaDB partial row events
dtunikov Jul 3, 2026
42385b1
Link MariaDB partial rows event docs instead of quoting event name
dtunikov Jul 3, 2026
c121b33
cleanup
dtunikov Jul 3, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
5 changes: 5 additions & 0 deletions docs/integrations/data-ingestion/clickpipes/mysql/faq.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -15,6 +15,11 @@ integration:
### Does the MySQL ClickPipe support MariaDB? {#does-the-clickpipe-support-mariadb}
Yes, the MySQL ClickPipe supports MariaDB 10.0 and above. The configuration for it is very similar to MySQL, using GTID replication by default.

### Why did my pipe fail with an unsupported MariaDB partial row event? {#mariadb-partial-row-event-unsupported}
MariaDB 12.3 and above can emit a [partial rows event](https://mariadb.com/docs/server/server-management/server-monitoring-logs/binary-log/row-binlog-events#partial_rows_log_event) in the binlog, which we don't support yet.

To recover, resync the pipe. To reduce the chance of hitting this again, you can also raise `binlog_row_event_fragment_threshold` setting on the source so fewer row changes get fragmented — keep it below your `max_allowed_packet`, since a single unfragmented binlog event larger than `max_allowed_packet` will fail the replication stream instead (see [Why is my pipe failing with a max_allowed_packet binlog error?](#binlog-event-exceeded-max-allowed-packet)).

### Does the MySQL ClickPipe support PlanetScale, Vitess, or TiDB? {#does-the-clickpipe-support-planetscale-vitess}
No, these don't support MySQL's binlog API.

Expand Down
Loading