Skip to content

docs: clarify column-level SELECT grants unsupported for MySQL/MariaDB CDC #3085

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
jwhartley merged 3 commits into from
Jul 3, 2026
Merged

docs: clarify column-level SELECT grants unsupported for MySQL/MariaDB CDC #3085

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
c01f8b0
docs: clarify column-level SELECT grants unsupported for MySQL/MariaD…
jwhartley Jun 29, 2026
5e51a24
docs: lead with binlog reason, rename section to 'Column-level permis…
jwhartley Jun 29, 2026
c673586
docs: fold column-level SELECT note into setup per review (aeluce)
jwhartley Jul 2, 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
6 changes: 4 additions & 2 deletions site/docs/reference/Connectors/capture-connectors/MariaDB/MariaDB.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -40,8 +40,10 @@ To meet these requirements, do the following:

1. Create the `flow_capture` user with replication permission, and the ability to read all tables.

The `SELECT` permission can be restricted to just the tables that need to be
captured, but automatic discovery requires `information_schema` access as well.
Grant `SELECT` on all tables or restrict it to the tables to be captured. `SELECT`
permissions must be at the table level, not the column level. Automatic discovery also
requires `information_schema` access. To keep specific columns, such as sensitive fields,
out of the capture, use [redaction](/features/redaction.md) rather than column-level grants.

```sql
CREATE USER IF NOT EXISTS flow_capture IDENTIFIED BY 'secret';
Expand Down
12 changes: 8 additions & 4 deletions site/docs/reference/Connectors/capture-connectors/MySQL/MySQL.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -54,8 +54,10 @@ To meet these requirements, follow the steps for your hosting type.

1. Create the `flow_capture` user with replication permission, and the ability to read all tables.

The `SELECT` permission can be restricted to just the tables that need to be
captured, but automatic discovery requires `information_schema` access as well.
Grant `SELECT` on all tables or restrict it to the tables to be captured. `SELECT`
permissions must be at the table level, not the column level. Automatic discovery also
requires `information_schema` access. To keep specific columns, such as sensitive fields,
out of the capture, use [redaction](/features/redaction.md) rather than column-level grants.

```sql
CREATE USER IF NOT EXISTS flow_capture
Expand Down Expand Up @@ -149,8 +151,10 @@ CALL mysql.rds_set_configuration('binlog retention hours', 168);
3. Using [MySQL workbench](https://docs.microsoft.com/en-us/azure/mysql/single-server/connect-workbench) or your preferred client,
create the `flow_capture` user with replication permission, and the ability to read all tables.

The `SELECT` permission can be restricted to just the tables that need to be
captured, but automatic discovery requires `information_schema` access as well.
Grant `SELECT` on all tables or restrict it to the tables to be captured. `SELECT`
permissions must be at the table level, not the column level. Automatic discovery also
requires `information_schema` access. To keep specific columns, such as sensitive fields,
out of the capture, use [redaction](/features/redaction.md) rather than column-level grants.

:::tip
Your username must be specified in the format `username@servername`.
Expand Down
Loading