From 992381eece03a641014adff23df9553a3b0e6ad8 Mon Sep 17 00:00:00 2001 From: Ti Chi Robot Date: Fri, 11 Oct 2024 18:05:01 +0800 Subject: [PATCH] ticdc: add description for pulsar topic config (#19049) (#19081) --- ticdc/ticdc-sink-to-pulsar.md | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/ticdc/ticdc-sink-to-pulsar.md b/ticdc/ticdc-sink-to-pulsar.md index 1898e13f6c1c9..b238156f6f58f 100644 --- a/ticdc/ticdc-sink-to-pulsar.md +++ b/ticdc/ticdc-sink-to-pulsar.md @@ -274,8 +274,9 @@ dispatchers = [ You can use `topic = "xxx"` to specify a topic dispatcher and use topic expressions to implement flexible topic dispatching policies. It is recommended that the total number of topics be less than 1000. -The format of a topic expression is `[prefix]{schema}[middle][{table}][suffix]`. The following are the meanings of each part: +The format of a topic expression is `[tenant_and_namespace][prefix]{schema}[middle][{table}][suffix]`. The following are the meanings of each part: +- `tenant_and_namespace`：Optional. Represents the tenant and namespace of the topic, such as `persistent://abc/def/`. If not configured, it means that the topic is in the default namespace `default` under the default tenant `public` of Pulsar. - `prefix`: Optional. Represents the prefix of the topic name. - `{schema}`: Optional. Represents the database name. - `middle`: Optional. Represents the separator between a database name and a table name.