Skip to content
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.

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

cdc: add more detail about the authorization (#19173) #19297

Merged
Merged
Changes from all commits
Commits
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
13 changes: 12 additions & 1 deletion ticdc/ticdc-sink-to-kafka.md
Original file line number Diff line number Diff line change
Expand Up @@ -149,7 +149,18 @@ The following are examples when using Kafka SASL authentication:
The minimum set of permissions required for TiCDC to function properly is as follows.

- The `Create`, `Write`, and `Describe` permissions for the Topic [resource type](https://docs.confluent.io/platform/current/kafka/authorization.html#resources).
- The `DescribeConfigs` permission for the Cluster resource type.
- The `DescribeConfig` permission for the Cluster resource type.

The usage scenarios for each permission are as follows:

| Resource type | Type of operation | Scenario |
| :-------------| :------------- | :--------------------------------|
| Cluster | `DescribeConfig`| Gets the cluster metadata while the changefeed is running |
| Topic | `Describe` | Tries to create a topic when the changefeed starts |
| Topic | `Create` | Tries to create a topic when the changefeed starts |
| Topic | `Write` | Sends data to the topic |

When creating or starting a changefeed, you can disable the `Describe` and `Create` permissions if the specified Kafka topic already exists.

### Integrate TiCDC with Kafka Connect (Confluent Platform)

Expand Down
Loading