DanielCarter-stack opened a new pull request, #11798:
URL: https://github.com/apache/seatunnel/pull/11798
## Purpose
Continue the per-connector Chinese docs improvement series for Greenplum,
MQTT and SQL Server, addressing the remaining zh-only files that passed the
open-PR ∪ last-7-days filter (`docs/zh/connectors/sink/Greenplum.md`,
`docs/zh/connectors/source/Mqtt.md`, `docs/zh/connectors/source/SqlServer.md`).
The corresponding English files are already in flight in other PRs, so they are
intentionally untouched in this batch.
The strict filter (open PR ∪ `git log --since=7d -- docs/`) only left three
files in zh this cycle, hence a 3-connector PR instead of the usual 5.
## Changes
### docs/zh/connectors/sink/Greenplum.md
- Rewrite the `## 主要特性` checklist so readers see `支持多表写入` and `定时刷新` flags
alongside the existing exactly-once/CDC markers.
- Add a `## 数据类型映射` section consistent with sibling JDBC sink docs (BOOLEAN,
SMALLINT, INT, BIGINT, DECIMAL, FLOAT, DOUBLE, STRING, DATE, TIME, TIMESTAMP,
BYTES).
- Extend the option table with `primary_keys`,
`connection_check_timeout_sec`, `max_commit_attempts`,
`transaction_timeout_sec` and `enable_upsert`, all of which are already
supported by the Jdbc Sink baseline.
- Add a CDC streaming example that wires `MySQL-CDC` to a `Jdbc` Greenplum
sink using `generate_sink_sql = true` plus `primary_keys = ["id"]`.
- Tighten the licence tip so readers know the native driver is intentionally
not bundled and that Greenplum does not support XA.
### docs/zh/connectors/source/Mqtt.md
- Replace the option table that was missing a `描述` column with a proper
5-column markdown table (名称 / 类型 / 是否必填 / 默认值 / 描述), keeping every existing
option but adding a row-level description for each one.
- Clarify the `url` option to mention `ssl://host:8883` alongside
`tcp://host:1883`, and the `qos` option to spell out the supported values.
- Add a `### TLS/SSL 接入` example and a `### 文本分隔源` example derived from the
connector's `field_delimiter` feature.
- Keep the original `### 持久会话源` example but make sure the snippet closes
with a `sink { Console {} }` clause so the fragment is runnable on its own.
### docs/zh/connectors/source/SqlServer.md
- Switch every task-example code fence from plain ``` to ```hocon so the
snippets render with VitePress syntax highlighting (the existing English
counterpart still uses plain fences — that will be fixed in a follow-up if the
English side becomes available again).
- Trim the duplicated verbose explanations out of the option table for
`split.even-distribution.factor.*`, `split.sample-sharding.threshold`,
`split.inverse-sampling.rate` and the `partition_*` options, then keep the full
descriptions under the `## 并行读取器` subsections instead of repeating them.
- Add a `### 整库多表读取` task example using `table_list`, plus a `### 自定义列裁剪示例`
example showing the `table_path` + `query` projection pattern.
- Modernize the 任务示例 source blocks (quote `password` so it parses cleanly)
and tighten the `## 提示` section guidance for `table_path`/`table_list` and the
`fetch_size`/`partition_column` recommendations.
## Verification
- Markdown fences were re-checked; each `\`\`\`hocon` block has a matching
close fence.
- The diff is docs-only — no Java/Markdown formatter or `mvnw verify` was
run since the change touches only `.md` files.
- No configuration keys were renamed or re-typed; only documentation
wording, table layout and example HOCON snippets were touched.
## Out of scope
- `docs/en/connectors/sink/Greenplum.md`,
`docs/en/connectors/source/Mqtt.md` and
`docs/en/connectors/source/SqlServer.md` are excluded because they are part of
other open PRs or were touched in the last 7 days.
- Other connector docs are untouched; they were either covered by recent PRs
or are already on the queue for a follow-up batch.
- Source code, tests and configuration files are not changed.
## Risk
Low. Docs-only changes; no behavioral change to connectors, option names or
defaults.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
