Skip to content

Create Source v2 (new syntax) docs for MySQL#36164

Open
patrickwwbutler wants to merge 4 commits intoMaterializeInc:mainfrom
patrickwwbutler:patrick/mysql-sv-docs-2
Open

Create Source v2 (new syntax) docs for MySQL#36164
patrickwwbutler wants to merge 4 commits intoMaterializeInc:mainfrom
patrickwwbutler:patrick/mysql-sv-docs-2

Conversation

@patrickwwbutler
Copy link
Copy Markdown
Contributor

Adds docs outlining how to use the new CREATE TABLE FROM SOURCE syntax for MySQL sources to enable source versioning

@patrickwwbutler patrickwwbutler requested a review from a team April 21, 2026 16:06
@patrickwwbutler patrickwwbutler marked this pull request as ready for review April 21, 2026 16:06
@patrickwwbutler patrickwwbutler requested a review from a team as a code owner April 21, 2026 16:06
Copy link
Copy Markdown
Member

@bosconi bosconi left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Here's what /mz-doc-edit came up with on its first time out of the garage.

Comment thread doc/user/content/sql/create-source/mysql-v2.md
Comment thread doc/user/content/sql/create-source/mysql-v2.md
Comment thread doc/user/content/sql/create-source/mysql-v2.md
Comment thread doc/user/content/sql/create-source/mysql-v2.md
Comment thread doc/user/content/sql/create-source/mysql-v2.md
Comment thread doc/user/content/sql/create-source/mysql-v2.md

See [`CREATE TABLE FROM SOURCE`](/sql/create-table/) for details.

#### Handling table schema changes
Copy link
Copy Markdown
Member

@bosconi bosconi Apr 21, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

rule_020 (section-split, conf 2): heading level skip — ## Ingesting data jumps to #### with no intervening ###. Promoting to ### makes this a peer of ### Change data capture and ### Monitoring source progress.

Suggested change
#### Handling table schema changes
### Handling table schema changes

Comment thread doc/user/content/sql/create-source/mysql-v2.md
patrickwwbutler and others added 2 commits April 21, 2026 19:21
Co-authored-by: Jon Currey <bosconi@users.noreply.github.com>
Co-authored-by: Jon Currey <bosconi@users.noreply.github.com>
Comment on lines +137 to +139
[//]: # "TODO(morsapaes) Replace this section with guidance using the new
progress metrics in mz_source_statistics + console monitoring, when available
(also for PostgreSQL)."
Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

rule_032 (comment-removal, conf 5): TODO(morsapaes) is a contributor name, not a tracked ticket — the carve-out for tracked issues does not apply.

Suggested change
[//]: # "TODO(morsapaes) Replace this section with guidance using the new
progress metrics in mz_source_statistics + console monitoring, when available
(also for PostgreSQL)."

Comment on lines +107 to +109
If you're running MySQL using a managed service, additional configuration
changes might be required. For step-by-step instructions on enabling GTID-based
binlog replication for your MySQL service, see the integration guides.
Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

rule_013 (tone-tightening, conf 2): shorten verbose cross-reference.

Suggested change
If you're running MySQL using a managed service, additional configuration
changes might be required. For step-by-step instructions on enabling GTID-based
binlog replication for your MySQL service, see the integration guides.
If you're running MySQL using a managed service, additional configuration
changes might be required. To enable GTID-based binlog replication for your
MySQL service, see the integration guides.

Comment on lines +166 to +167
database. For more details on monitoring source ingestion progress and debugging
related issues, see [Troubleshooting](/ops/troubleshooting/).
Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

rule_013 (tone-tightening, conf 2): shorten verbose cross-reference.

Suggested change
database. For more details on monitoring source ingestion progress and debugging
related issues, see [Troubleshooting](/ops/troubleshooting/).
database. For more information, see [Troubleshooting](/ops/troubleshooting/).

Comment on lines +193 to +195
Once created, a connection is **reusable** across multiple `CREATE SOURCE`
statements. For more details on creating connections, check the
[`CREATE CONNECTION`](/sql/create-connection/#mysql) documentation page.
Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

rule_013 (tone-tightening, conf 2): shorten verbose cross-reference.

Suggested change
Once created, a connection is **reusable** across multiple `CREATE SOURCE`
statements. For more details on creating connections, check the
[`CREATE CONNECTION`](/sql/create-connection/#mysql) documentation page.
Once created, a connection is **reusable** across multiple `CREATE SOURCE`
statements. For more information, see [`CREATE CONNECTION`](/sql/create-connection/#mysql).

Comment on lines +232 to +234
For step-by-step instructions on creating AWS PrivateLink connections and
configuring an AWS PrivateLink service to accept connections from Materialize,
check [this guide](/ops/network-security/privatelink/).
Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

rule_013 (tone-tightening, conf 2): shorten verbose cross-reference.

Suggested change
For step-by-step instructions on creating AWS PrivateLink connections and
configuring an AWS PrivateLink service to accept connections from Materialize,
check [this guide](/ops/network-security/privatelink/).
For more information, see [this guide](/ops/network-security/privatelink/).

Comment on lines +254 to +256
For step-by-step instructions on creating SSH tunnel connections and configuring
an SSH bastion server to accept connections from Materialize, check
[this guide](/ops/network-security/ssh-tunnel/).
Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

rule_013 (tone-tightening, conf 2): shorten verbose cross-reference.

Suggested change
For step-by-step instructions on creating SSH tunnel connections and configuring
an SSH bastion server to accept connections from Materialize, check
[this guide](/ops/network-security/ssh-tunnel/).
For more information, see [this guide](/ops/network-security/ssh-tunnel/).


See [`CREATE TABLE FROM SOURCE`](/sql/create-table/#handling-table-schema-changes) for details.

#### Supported types
Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

rule_020 (section-split, conf 2): heading level skip — promote to ### for consistent hierarchy.

Suggested change
#### Supported types
### Supported types

For more information, including strategies for handling unsupported types,
see [`CREATE TABLE FROM SOURCE`](/sql/create-table/).

#### Upstream table truncation restrictions
Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

rule_020 (section-split, conf 2): heading level skip — promote to ### for consistent hierarchy.

Suggested change
#### Upstream table truncation restrictions
### Upstream table truncation restrictions

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants