Mention schema changes not supported on MySQL 5.x #5226
+3
−1
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
The latest updates on your projects. Learn more about Vercel for GitHub.
3 Skipped Deployments
|
jgao54
approved these changes
Jan 13, 2026
Member
Author
|
Waiting on internal discussions to happen before checking in. |
whites11
approved these changes
Jan 14, 2026
Blargian
approved these changes
Jan 14, 2026
morsapaes
reviewed
Jan 14, 2026
| :::note | ||
|
|
||
| Column exclusion is not supported for MySQL 5.7 because the `binlog_row_metadata` setting wasn't yet introduced. | ||
| Column exclusion and schema changes are not supported for MySQL 5.7 because the `binlog_row_metadata` setting wasn't yet introduced. |
Contributor
There was a problem hiding this comment.
Suggested change
| Column exclusion and schema changes are not supported for MySQL 5.7 because the `binlog_row_metadata` setting wasn't yet introduced. | |
| Column exclusion and schema changes are not supported for MySQL 5.7 and older versions. These features depend on table metadata not available in the binlog prior to [MySQL 8.0.1](https://dev.mysql.com/blog-archive/more-metadata-is-written-into-binary-log/). |
morsapaes
reviewed
Jan 14, 2026
| | Adding a new column with a default value (`ALTER TABLE ADD COLUMN ... DEFAULT ...`) | Propagated automatically. The new column(s) will be populated for all rows replicated after the schema change, but existing rows will not show the default value without a full table refresh | | ||
| | Dropping an existing column (`ALTER TABLE DROP COLUMN ...`) | Detected, but **not** propagated. The dropped column(s) will be populated with `NULL` for all rows replicated after the schema change | | ||
|
|
||
| **Schema changes on MySQL 5.x are not supported**, as reliably tracking columns depends on `binlog_row_metadata` which was added in MySQL 8.0. |
Contributor
There was a problem hiding this comment.
Suggested change
| **Schema changes on MySQL 5.x are not supported**, as reliably tracking columns depends on `binlog_row_metadata` which was added in MySQL 8.0. | |
| **Schema changes are not supported for MySQL 5.7 and older versions**. Reliably tracking columns depends on on table metadata not available in the binlog prior to [MySQL 8.0.1](https://dev.mysql.com/blog-archive/more-metadata-is-written-into-binary-log/). |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Summary
Mention schema changes in ClickPipes are not supported on MySQL 5.x
Checklist