This is an automated email from the ASF dual-hosted git repository.

github-merge-queue[bot] pushed a commit to branch 
gh-readonly-queue/dev/pr-12981-f07b3ccfad1a440c081401c3588fe9bd84187740
in repository https://gitbox.apache.org/repos/asf/seatunnel.git

commit 01cba7d92191227430db1e47318d37ea0b794ce5
Author: HouKangle <[email protected]>
AuthorDate: Mon Nov 9 12:53:25 2026 +0000

    [Docs][Transform-V2] Improve FieldMapper documentation (#12981)
---
 docs/en/transforms/field-mapper.md | 307 +++++++++++++++++++++++++++++++++----
 docs/zh/transforms/field-mapper.md | 307 +++++++++++++++++++++++++++++++++----
 2 files changed, 556 insertions(+), 58 deletions(-)

diff --git a/docs/en/transforms/field-mapper.md 
b/docs/en/transforms/field-mapper.md
index 4d8ae66dd8..322a7f9e64 100644
--- a/docs/en/transforms/field-mapper.md
+++ b/docs/en/transforms/field-mapper.md
@@ -2,63 +2,312 @@
 
 > FieldMapper transform plugin
 
+## Support Those Engines
+
+> Spark<br/>
+> Flink<br/>
+> SeaTunnel Zeta<br/>
+
 ## Description
 
-Add input schema and output schema mapping.
+FieldMapper selects input fields and maps their names to output field names. 
Use it to rename or reorder fields and remove fields that a downstream sink 
does not need. Only fields included in `field_mapper` remain in the output; 
their values and data types are preserved. The table path does not change. For 
sources that produce multiple tables, you can configure a shared mapping and 
override it with complete per-table mappings.
 
 ## Options
 
-|     name     |  type  | required | default value |
-|--------------|--------|----------|---------------|
-| field_mapper | Object | yes      |               |
+| Name | Type | Required | Default | Description |
+|------|------|----------|---------|-------------|
+| field_mapper | Map&lt;String, String&gt; | conditionally yes | - | Non-empty 
mapping from input field names to output field names. Required at the transform 
level when `table_transform` is absent or empty, and in every `table_transform` 
entry. |
+| table_match_regex | String | no | `.*` | Regular expression selecting the 
table paths to which the transform-level mapping applies. |
+| table_transform | Array&lt;Map&gt; | no | `[]` | Complete mappings for 
individual tables, selected by exact `table_path`. |
+| rule_match_mode | String | no | `FIRST_MATCH` | How multiple entries with 
the same `table_path` are applied. Must be set explicitly to allow duplicate 
paths. |
+| common options | - | no | - | Dataset wiring options; see [Transform Common 
Options](common-options/common-options.md). |
+
+### field_mapper [Map&lt;String, String&gt;]
+
+Each key is an existing input field name, and its value is the output field 
name. For example, `name = display_name` renames `name` to `display_name`, 
while `id = id` retains `id` with its original name. Fields not listed as keys 
are removed. This option changes field selection and names, not field values or 
types.
+
+The mapping must not be empty. Every key must exist in the input schema of the 
table receiving this rule; a missing field causes transform initialization to 
fail. When `table_transform` contains entries, the transform-level 
`field_mapper` may be omitted. If it is supplied, it must still be a valid 
non-empty mapping.
+
+Primary keys and constraint keys are retained, with their column names mapped, 
only when all of their columns remain in the output.
+
+Output columns follow the mapping order, rather than the input schema order. 
For example, `field_mapper = { name = display_name, id = id }` produces 
`display_name` followed by `id`, even when the input schema starts with `id`.
+
+### table_match_regex [String]
+
+A regular expression matched against the entire upstream table path. The 
default `.*` matches every table. For example, `demo[.](users|admins)` matches 
`demo.users` and `demo.admins`.
+
+This option selects tables for the transform-level `field_mapper` only. It 
does not restrict explicit `table_transform` entries. It matches actual table 
paths, not dataset names such as `plugin_input` or `plugin_output`. If there is 
no transform-level mapping, this option does not create one.
+
+### table_transform [Array&lt;Map&gt;]
+
+A list of per-table rules. Each entry must contain:
+
+- `table_path`: a non-blank string exactly matching the upstream table path, 
for example `demo.admins`.
+- `field_mapper`: a complete, non-empty mapping for that table.
+
+An entry takes precedence over the transform-level mapping and does not 
inherit its fields. In particular, a field retained by the transform-level 
mapping is still removed from an explicitly matched table if its per-table 
mapping omits that field. The default is an empty list.
+
+### rule_match_mode [String]
+
+Controls entries in `table_transform` that have the same `table_path`:
+
+- `FIRST_MATCH`: apply the first matching entry only.
+- `ALL_MATCH`: apply all matching entries in list order. Each mapping receives 
the schema and rows produced by the previous mapping, so its keys must refer to 
fields that still exist under their current names.
+
+Although the default is `FIRST_MATCH`, omitting this option rejects duplicate 
`table_path` entries. Set `rule_match_mode` explicitly to `FIRST_MATCH` or 
`ALL_MATCH` when duplicate paths are intentional.
 
-### field_mapper [config]
+### common options
 
-Specify the field mapping relationship between input and output
+Use `plugin_input` and `plugin_output` to connect the transform to named 
datasets. See [Transform Common Options](common-options/common-options.md) for 
wiring behavior and deprecated option names. These dataset names do not rename 
the tables inside the dataset.
 
-### common options [config]
+## Multi-Table Configuration
 
-Transform plugin common parameters, please refer to [Transform 
Plugin](common-options/common-options.md) for details.
+For each upstream table, FieldMapper resolves the mapping in this order:
+
+1. If there is an exact `table_transform` entry, apply the selected per-table 
rule or rules.
+2. Otherwise, if a transform-level `field_mapper` exists and the table path 
matches `table_match_regex`, apply that mapping.
+3. Otherwise, pass the table through with its schema and rows unchanged.
+
+When only `table_transform` is configured, tables without an entry remain 
unchanged. Every entry is validated independently, even when a transform-level 
mapping is also present. See [Multi-Table Transform](transform-multi-table.md) 
for the shared behavior.
 
 ## Example
 
-The data read from source is a table like this:
+The following complete batch configurations use FakeSource with explicit rows 
and Console output. They require the FakeSource and Console connectors. Column 
values in the result tables are identified by name; Console log formatting may 
differ.
+
+### Transform-level mapping only
+
+Input table `demo.users`:
+
+| id | name | age |
+|----|------|-----|
+| 1 | Alice | 20 |
 
-| id |   name   | age | card |
-|----|----------|-----|------|
-| 1  | Joy Ding | 20  | 123  |
-| 2  | May Ding | 20  | 123  |
-| 3  | Kin Dom  | 20  | 123  |
-| 4  | Joy Dom  | 20  | 123  |
+Keep `id`, rename `name` to `display_name`, and remove `age`:
+
+```hocon
+env {
+  parallelism = 1
+  job.mode = "BATCH"
+}
+
+source {
+  FakeSource {
+    plugin_output = "input"
+    schema {
+      table = "demo.users"
+      columns = [
+        { name = "id", type = "int" },
+        { name = "name", type = "string" },
+        { name = "age", type = "int" }
+      ]
+    }
+    rows = [{ kind = INSERT, fields = [1, "Alice", 20] }]
+  }
+}
 
-We want to delete `age` field and update the field order to `id`, `card`, 
`name` and rename `name` to `new_name`. We can add `FieldMapper` transform like 
this
+transform {
+  FieldMapper {
+    plugin_input = "input"
+    plugin_output = "mapped"
+    field_mapper = {
+      id = id
+      name = display_name
+    }
+  }
+}
 
+sink {
+  Console {
+    plugin_input = "mapped"
+  }
+}
 ```
+
+Output table `demo.users`:
+
+| id | display_name |
+|----|--------------|
+| 1 | Alice |
+
+### Transform-level mapping with a per-table override
+
+The input dataset contains three tables, each with the schema `id INT, name 
STRING, age INT`:
+
+| Table path | id | name | age |
+|------------|----|------|-----|
+| demo.users | 1 | Alice | 20 |
+| demo.admins | 2 | Bob | 30 |
+| demo.audit | 3 | Carol | 40 |
+
+The regex matches both `demo.users` and `demo.admins`, but the explicit 
mapping for `demo.admins` takes precedence. `demo.audit` matches neither rule 
and remains unchanged.
+
+```hocon
+env {
+  parallelism = 1
+  job.mode = "BATCH"
+}
+
+source {
+  FakeSource {
+    plugin_output = "input"
+    tables_configs = [
+      {
+        schema {
+          table = "demo.users"
+          columns = [
+            { name = "id", type = "int" },
+            { name = "name", type = "string" },
+            { name = "age", type = "int" }
+          ]
+        }
+        rows = [{ kind = INSERT, fields = [1, "Alice", 20] }]
+      },
+      {
+        schema {
+          table = "demo.admins"
+          columns = [
+            { name = "id", type = "int" },
+            { name = "name", type = "string" },
+            { name = "age", type = "int" }
+          ]
+        }
+        rows = [{ kind = INSERT, fields = [2, "Bob", 30] }]
+      },
+      {
+        schema {
+          table = "demo.audit"
+          columns = [
+            { name = "id", type = "int" },
+            { name = "name", type = "string" },
+            { name = "age", type = "int" }
+          ]
+        }
+        rows = [{ kind = INSERT, fields = [3, "Carol", 40] }]
+      }
+    ]
+  }
+}
+
 transform {
   FieldMapper {
-    plugin_input = "fake"
-    plugin_output = "fake1"
+    plugin_input = "input"
+    plugin_output = "mapped"
+    table_match_regex = "demo[.](users|admins)"
     field_mapper = {
-        id = id
-        card = card
-        name = new_name
+      id = id
+      name = display_name
     }
+    table_transform = [
+      {
+        table_path = "demo.admins"
+        field_mapper = {
+          id = admin_id
+          name = admin_name
+        }
+      }
+    ]
+  }
+}
+
+sink {
+  Console {
+    plugin_input = "mapped"
   }
 }
 ```
 
-Then the data in result table `fake1` will like this
+Expected output, shown as field-name/value pairs:
+
+| Table path | Output fields and values |
+|------------|--------------------------|
+| demo.users | `id = 1`, `display_name = "Alice"` |
+| demo.admins | `admin_id = 2`, `admin_name = "Bob"` |
+| demo.audit | `id = 3`, `name = "Carol"`, `age = 40` |
+
+### Per-table mapping only
 
-| id | card | new_name |
-|----|------|----------|
-| 1  | 123  | Joy Ding |
-| 2  | 123  | May Ding |
-| 3  | 123  | Kin Dom  |
-| 4  | 123  | Joy Dom  |
+This configuration uses the same input tables and rows as the preceding 
example. It omits the transform-level mapping, so only `demo.admins` is 
transformed. Both `demo.users` and `demo.audit` remain unchanged.
+
+```hocon
+env {
+  parallelism = 1
+  job.mode = "BATCH"
+}
+
+source {
+  FakeSource {
+    plugin_output = "input"
+    tables_configs = [
+      {
+        schema {
+          table = "demo.users"
+          columns = [
+            { name = "id", type = "int" },
+            { name = "name", type = "string" },
+            { name = "age", type = "int" }
+          ]
+        }
+        rows = [{ kind = INSERT, fields = [1, "Alice", 20] }]
+      },
+      {
+        schema {
+          table = "demo.admins"
+          columns = [
+            { name = "id", type = "int" },
+            { name = "name", type = "string" },
+            { name = "age", type = "int" }
+          ]
+        }
+        rows = [{ kind = INSERT, fields = [2, "Bob", 30] }]
+      },
+      {
+        schema {
+          table = "demo.audit"
+          columns = [
+            { name = "id", type = "int" },
+            { name = "name", type = "string" },
+            { name = "age", type = "int" }
+          ]
+        }
+        rows = [{ kind = INSERT, fields = [3, "Carol", 40] }]
+      }
+    ]
+  }
+}
+
+transform {
+  FieldMapper {
+    plugin_input = "input"
+    plugin_output = "mapped"
+    table_transform = [
+      {
+        table_path = "demo.admins"
+        field_mapper = {
+          id = admin_id
+          name = admin_name
+        }
+      }
+    ]
+  }
+}
+
+sink {
+  Console {
+    plugin_input = "mapped"
+  }
+}
+```
+
+Expected output:
+
+| Table path | Output fields and values |
+|------------|--------------------------|
+| demo.users | `id = 1`, `name = "Alice"`, `age = 20` |
+| demo.admins | `admin_id = 2`, `admin_name = "Bob"` |
+| demo.audit | `id = 3`, `name = "Carol"`, `age = 40` |
 
 ## Changelog
 
 ### new version
 
 - Add FieldMapper Transform Connector
-
diff --git a/docs/zh/transforms/field-mapper.md 
b/docs/zh/transforms/field-mapper.md
index 64eb8e1c7b..e5569db521 100644
--- a/docs/zh/transforms/field-mapper.md
+++ b/docs/zh/transforms/field-mapper.md
@@ -2,63 +2,312 @@
 
 > 字段映射转换插件
 
+## 支持的引擎
+
+> Spark<br/>
+> Flink<br/>
+> SeaTunnel Zeta<br/>
+
 ## 描述
 
-添加输入模式和输出模式映射
+FieldMapper 选择输入字段,并将其名称映射为输出字段名称。适用于字段重命名、调整字段顺序,以及删除下游 Sink 不需要的字段。只有 
`field_mapper` 
中指定的字段会保留在输出中,字段值和数据类型保持不变,表路径也不会改变。当数据源输出多张表时,可以配置共享映射,并通过完整的表级映射覆盖它。
 
 ## 属性
 
-|      名称      |   类型   | 是否必须 | 默认值 |
-|--------------|--------|------|-----|
-| field_mapper | Object | yes  |     |
+| 名称 | 类型 | 是否必须 | 默认值 | 描述 |
+|------|------|----------|--------|------|
+| field_mapper | Map&lt;String, String&gt; | 条件必填 | - | 从输入字段名到输出字段名的非空映射。未配置 
`table_transform` 或其为空列表时,转换级别必须配置此项;每个 `table_transform` 条目也必须配置此项。 |
+| table_match_regex | String | 否 | `.*` | 用于选择应用转换级别映射的表路径的正则表达式。 |
+| table_transform | Array&lt;Map&gt; | 否 | `[]` | 通过精确匹配 `table_path` 
为各表指定完整映射。 |
+| rule_match_mode | String | 否 | `FIRST_MATCH` | 相同 `table_path` 
的多个条目的应用方式。允许重复路径时必须显式配置。 |
+| common options | - | 否 | - | 
数据集连接参数,参见[转换插件通用配置](common-options/common-options.md)。 |
+
+### field_mapper [Map&lt;String, String&gt;]
+
+每个键是已有的输入字段名,对应的值是输出字段名。例如,`name = display_name` 将 `name` 重命名为 
`display_name`,而 `id = id` 按原名称保留 `id`。未列为键的字段会被删除。此选项只改变字段选择和名称,不改变字段值或类型。
+
+映射不能为空。每个键都必须存在于应用此规则的表的输入模式中;字段不存在会导致转换初始化失败。当 `table_transform` 
包含条目时,可以省略转换级别的 `field_mapper`。如果提供了该选项,它仍然必须是有效的非空映射。
+
+只有主键或约束键包含的所有列都保留在输出中时,才会保留该主键或约束键,并同步映射其列名。
+
+输出列遵循映射顺序,而不是输入模式的字段顺序。例如,`field_mapper = { name = display_name, id = id }` 
的输出列依次为 `display_name` 和 `id`,即使输入模式以 `id` 开头也是如此。
+
+### table_match_regex [String]
+
+与上游完整表路径匹配的正则表达式。默认值 `.*` 匹配所有表。例如,`demo[.](users|admins)` 匹配 `demo.users` 和 
`demo.admins`。
+
+此选项只用于选择应用转换级别 `field_mapper` 的表,不限制显式指定的 `table_transform` 条目。它匹配实际表路径,而不是 
`plugin_input` 或 `plugin_output` 等数据集名称。没有转换级别映射时,此选项不会创建映射规则。
+
+### table_transform [Array&lt;Map&gt;]
+
+表级规则列表。每个条目必须包含:
+
+- `table_path`:与上游表路径精确匹配的非空白字符串,例如 `demo.admins`。
+- `field_mapper`:该表完整的非空映射。
+
+表级条目优先于转换级别映射,并且不会继承其中的字段。即使转换级别映射保留了某个字段,如果精确匹配的表级映射省略了它,该字段仍然会被删除。此选项默认为空列表。
+
+### rule_match_mode [String]
+
+控制 `table_transform` 中具有相同 `table_path` 的多个条目的应用方式:
+
+- `FIRST_MATCH`:只应用第一个匹配条目。
+- `ALL_MATCH`:按列表顺序应用所有匹配条目。每次映射接收上一次映射产生的模式和行,因此其键必须使用仍然存在的字段的当前名称。
+
+虽然默认值为 `FIRST_MATCH`,但省略此选项时,重复的 `table_path` 会被拒绝。如果需要为同一路径配置多个条目,必须显式将 
`rule_match_mode` 设置为 `FIRST_MATCH` 或 `ALL_MATCH`。
 
-### field_mapper [config]
+### common options
 
-指定输入和输出之间的字段映射关系
+通过 `plugin_input` 和 `plugin_output` 
将转换连接到命名数据集。有关连接行为和已弃用的选项名称,参见[转换插件通用配置](common-options/common-options.md)。这些数据集名称不会重命名数据集中的表。
 
-### common options [config]
+## 多表配置
 
-转换插件的常见参数, 请参考  [Transform Plugin](common-options/common-options.md) 了解详情
+对于每张上游表,FieldMapper 按以下顺序确定映射规则:
+
+1. 如果存在精确匹配的 `table_transform` 条目,则应用选中的一条或多条表级规则。
+2. 否则,如果存在转换级别的 `field_mapper`,且表路径匹配 `table_match_regex`,则应用该映射。
+3. 否则,原样传递该表,其模式和行均保持不变。
+
+只配置 `table_transform` 
时,没有匹配条目的表保持不变。每个条目都会独立校验,即使同时存在转换级别映射也是如此。共享行为的详细说明参见[多表转换](transform-multi-table.md)。
 
 ## 示例
 
-源端数据读取的表格如下:
+以下完整批处理配置使用 FakeSource 提供显式数据行,并通过 Console 输出结果,需要安装 FakeSource 和 Console 
连接器。结果表按字段名标识值,Console 日志的实际显示格式可能不同。
+
+### 仅使用转换级别映射
+
+输入表 `demo.users`:
+
+| id | name | age |
+|----|------|-----|
+| 1 | Alice | 20 |
 
-| id |   name   | age | card |
-|----|----------|-----|------|
-| 1  | Joy Ding | 20  | 123  |
-| 2  | May Ding | 20  | 123  |
-| 3  | Kin Dom  | 20  | 123  |
-| 4  | Joy Dom  | 20  | 123  |
+保留 `id`,将 `name` 重命名为 `display_name`,并删除 `age`:
+
+```hocon
+env {
+  parallelism = 1
+  job.mode = "BATCH"
+}
+
+source {
+  FakeSource {
+    plugin_output = "input"
+    schema {
+      table = "demo.users"
+      columns = [
+        { name = "id", type = "int" },
+        { name = "name", type = "string" },
+        { name = "age", type = "int" }
+      ]
+    }
+    rows = [{ kind = INSERT, fields = [1, "Alice", 20] }]
+  }
+}
 
-我们想要删除 `age` 字段,并更新字段顺序为 `id`、`card`、`name`,同时将 `name` 重命名为 
`new_name`。我们可以像这样添加 `FieldMapper` 转换:
+transform {
+  FieldMapper {
+    plugin_input = "input"
+    plugin_output = "mapped"
+    field_mapper = {
+      id = id
+      name = display_name
+    }
+  }
+}
 
+sink {
+  Console {
+    plugin_input = "mapped"
+  }
+}
 ```
+
+输出表 `demo.users`:
+
+| id | display_name |
+|----|--------------|
+| 1 | Alice |
+
+### 转换级别映射与表级覆盖规则
+
+输入数据集包含三张表,每张表的模式均为 `id INT, name STRING, age INT`:
+
+| 表路径 | id | name | age |
+|--------|----|------|-----|
+| demo.users | 1 | Alice | 20 |
+| demo.admins | 2 | Bob | 30 |
+| demo.audit | 3 | Carol | 40 |
+
+正则表达式同时匹配 `demo.users` 和 `demo.admins`,但 `demo.admins` 的显式映射优先生效。`demo.audit` 
不匹配任何规则,因此保持不变。
+
+```hocon
+env {
+  parallelism = 1
+  job.mode = "BATCH"
+}
+
+source {
+  FakeSource {
+    plugin_output = "input"
+    tables_configs = [
+      {
+        schema {
+          table = "demo.users"
+          columns = [
+            { name = "id", type = "int" },
+            { name = "name", type = "string" },
+            { name = "age", type = "int" }
+          ]
+        }
+        rows = [{ kind = INSERT, fields = [1, "Alice", 20] }]
+      },
+      {
+        schema {
+          table = "demo.admins"
+          columns = [
+            { name = "id", type = "int" },
+            { name = "name", type = "string" },
+            { name = "age", type = "int" }
+          ]
+        }
+        rows = [{ kind = INSERT, fields = [2, "Bob", 30] }]
+      },
+      {
+        schema {
+          table = "demo.audit"
+          columns = [
+            { name = "id", type = "int" },
+            { name = "name", type = "string" },
+            { name = "age", type = "int" }
+          ]
+        }
+        rows = [{ kind = INSERT, fields = [3, "Carol", 40] }]
+      }
+    ]
+  }
+}
+
 transform {
   FieldMapper {
-    plugin_input = "fake"
-    plugin_output = "fake1"
+    plugin_input = "input"
+    plugin_output = "mapped"
+    table_match_regex = "demo[.](users|admins)"
     field_mapper = {
-        id = id
-        card = card
-        name = new_name
+      id = id
+      name = display_name
     }
+    table_transform = [
+      {
+        table_path = "demo.admins"
+        field_mapper = {
+          id = admin_id
+          name = admin_name
+        }
+      }
+    ]
+  }
+}
+
+sink {
+  Console {
+    plugin_input = "mapped"
   }
 }
 ```
 
-那么结果表 `fake1` 中的数据将会像这样:
+预期输出,以字段名和值展示:
+
+| 表路径 | 输出字段和值 |
+|--------|--------------|
+| demo.users | `id = 1`, `display_name = "Alice"` |
+| demo.admins | `admin_id = 2`, `admin_name = "Bob"` |
+| demo.audit | `id = 3`, `name = "Carol"`, `age = 40` |
+
+### 仅使用表级映射
 
-| id | card | new_name |
-|----|------|----------|
-| 1  | 123  | Joy Ding |
-| 2  | 123  | May Ding |
-| 3  | 123  | Kin Dom  |
-| 4  | 123  | Joy Dom  |
+此配置使用与上一示例相同的输入表和数据行。由于省略了转换级别映射,只有 `demo.admins` 会被转换,`demo.users` 和 
`demo.audit` 均保持不变。
+
+```hocon
+env {
+  parallelism = 1
+  job.mode = "BATCH"
+}
+
+source {
+  FakeSource {
+    plugin_output = "input"
+    tables_configs = [
+      {
+        schema {
+          table = "demo.users"
+          columns = [
+            { name = "id", type = "int" },
+            { name = "name", type = "string" },
+            { name = "age", type = "int" }
+          ]
+        }
+        rows = [{ kind = INSERT, fields = [1, "Alice", 20] }]
+      },
+      {
+        schema {
+          table = "demo.admins"
+          columns = [
+            { name = "id", type = "int" },
+            { name = "name", type = "string" },
+            { name = "age", type = "int" }
+          ]
+        }
+        rows = [{ kind = INSERT, fields = [2, "Bob", 30] }]
+      },
+      {
+        schema {
+          table = "demo.audit"
+          columns = [
+            { name = "id", type = "int" },
+            { name = "name", type = "string" },
+            { name = "age", type = "int" }
+          ]
+        }
+        rows = [{ kind = INSERT, fields = [3, "Carol", 40] }]
+      }
+    ]
+  }
+}
+
+transform {
+  FieldMapper {
+    plugin_input = "input"
+    plugin_output = "mapped"
+    table_transform = [
+      {
+        table_path = "demo.admins"
+        field_mapper = {
+          id = admin_id
+          name = admin_name
+        }
+      }
+    ]
+  }
+}
+
+sink {
+  Console {
+    plugin_input = "mapped"
+  }
+}
+```
+
+预期输出:
+
+| 表路径 | 输出字段和值 |
+|--------|--------------|
+| demo.users | `id = 1`, `name = "Alice"`, `age = 20` |
+| demo.admins | `admin_id = 2`, `admin_name = "Bob"` |
+| demo.audit | `id = 3`, `name = "Carol"`, `age = 40` |
 
 ## 更新日志
 
 ### 新版本
 
 - 添加 FieldMapper 转换插件
-

Reply via email to