This is an automated email from the ASF dual-hosted git repository.
lzljs3620320 pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/incubator-paimon.git
The following commit(s) were added to refs/heads/master by this push:
new b9073afbb [hotfix] Fix doc build error
b9073afbb is described below
commit b9073afbb07a928026a76bf5dc7b64d82cea513f
Author: JingsongLi <[email protected]>
AuthorDate: Thu Apr 20 14:31:28 2023 +0800
[hotfix] Fix doc build error
---
docs/content/how-to/cdc-ingestion.md | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/docs/content/how-to/cdc-ingestion.md
b/docs/content/how-to/cdc-ingestion.md
index 282b5c1a8..19315d896 100644
--- a/docs/content/how-to/cdc-ingestion.md
+++ b/docs/content/how-to/cdc-ingestion.md
@@ -57,7 +57,7 @@ To use this feature through `flink run`, run the following
shell command.
* `--partition-keys` are the partition keys for Paimon table. If there are
multiple partition keys, connect them with comma, for example `dt,hh,mm`.
* `--primary-keys` are the primary keys for Paimon table. If there are
multiple primary keys, connect them with comma, for example
`buyer_id,seller_id`.
* `--mysql-conf` is the configuration for Flink CDC MySQL table sources. Each
configuration should be specified in the format `key=value`. `hostname`,
`username`, `password`, `database-name` and `table-name` are required
configurations, others are optional. See its
[document](https://ververica.github.io/flink-cdc-connectors/master/content/connectors/mysql-cdc.html#connector-options)
for a complete list of configurations.
-* `--catalog-conf` is the configuration for Paimon catalog. Each configuration
should be specified in the format `key=value`. See [here]({{< ref
"maintenance/configurations/" >}}) for a complete list of catalog
configurations.
+* `--catalog-conf` is the configuration for Paimon catalog. Each configuration
should be specified in the format `key=value`. See [here]({{< ref
"maintenance/configurations" >}}) for a complete list of catalog configurations.
* `--table-conf` is the configuration for Paimon table sink. Each
configuration should be specified in the format `key=value`. See [here]({{< ref
"maintenance/configurations" >}}) for a complete list of table configurations.
If the Paimon table you specify does not exist, this action will automatically
create the table. Its schema will be derived from all specified MySQL tables.
If the Paimon table already exists, its schema will be compared against the
schema of all specified MySQL tables.
@@ -120,7 +120,7 @@ To use this feature through `flink run`, run the following
shell command.
* `--warehouse` is the path to Paimon warehouse.
* `--database` is the database name in Paimon catalog.
* `--mysql-conf` is the configuration for Flink CDC MySQL table sources. Each
configuration should be specified in the format `key=value`. `hostname`,
`username`, `password` and `database-name` are required configurations, others
are optional. Note that `database-name` should be the exact name of the MySQL
databse you want to synchronize. It can't be a regular expression. See its
[document](https://ververica.github.io/flink-cdc-connectors/master/content/connectors/mysql-cdc.html#connecto
[...]
-* `--catalog-conf` is the configuration for Paimon catalog. Each configuration
should be specified in the format `key=value`. See [here]({{< ref
"maintenance/configurations/" >}}) for a complete list of catalog
configurations.
+* `--catalog-conf` is the configuration for Paimon catalog. Each configuration
should be specified in the format `key=value`. See [here]({{< ref
"maintenance/configurations" >}}) for a complete list of catalog configurations.
* `--table-conf` is the configuration for Paimon table sink. Each
configuration should be specified in the format `key=value`. All Paimon sink
table will be applied the same set of configurations. See [here]({{< ref
"maintenance/configurations" >}}) for a complete list of table configurations.
For each MySQL table to be synchronized, if the corresponding Paimon table
does not exist, this action will automatically create the table. Its schema
will be derived from all specified MySQL tables. If the Paimon table already
exists, its schema will be compared against the schema of all specified MySQL
tables.
