zhzjzz opened a new pull request, #12981: URL: https://github.com/apache/seatunnel/pull/12981
### Purpose of this pull request Yes, I am contributing this documentation update to Apache SeaTunnel. Part of #12809. The FieldMapper pages currently omit the multi-table options and provide only a transform fragment. This change rewrites both English and Chinese pages with a five-column options table, per-option explanations, mapping precedence, and complete FakeSource-to-Console examples. The examples cover a transform-level mapping, a per-table override with an unmatched table passing through, and a configuration containing only per-table rules. Each example includes input and expected output data. The text explains field removal and ordering, required mappings, exact table-path matching, and the explicit `rule_match_mode` requirement for duplicate table paths. Only `docs/en/transforms/field-mapper.md` and `docs/zh/transforms/field-mapper.md` change. Options and behavior were checked against `FieldMapperTransformConfig`, `FieldMapperTransformFactory`, `FieldMapperTransform`, `FieldMapperMultiCatalogTransform`, `TransformCommonOptions`, and `AbstractMultiCatalogTransform`. Claim: https://github.com/apache/seatunnel/issues/12809#issuecomment-6381330046. Maintainer confirmation of the claim is still pending at preparation time. ### Does this PR introduce _any_ user-facing change? Yes, documentation becomes complete and consistent across EN/ZH. For example, a per-table mapping replaces the transform-level mapping for that table, while a table matched by neither rule passes through unchanged. Runtime behavior, APIs and configuration defaults are unchanged. ### How was this patch tested? Validated on Windows with JDK 17 and Maven 3.9.11, based on dev commit `9ab97e15f33cd1383c5216e50e77a2fe53d212c3`. - Root `mvn spotless:apply`: passed. - Focused reactor `verify`: passed in 13 modules; 24 existing configuration and FieldMapper/multi-table tests passed, with zero failures, errors or skips. - Existing `MarkdownTest`: three tests passed; one is explicitly disabled on Windows. - A temporary local validation harness extracted all six EN/ZH configuration blocks, checked cross-language parity, and used SeaTunnel's actual parser, factory option rules, FakeSource row generator, FieldMapper and Console writer. All 14 documented output rows matched their expected schema, table path, values and types. A separate reversed mapping verified column ordering. This was in-process validation, not an engine-cluster E2E run. The harness is not included in this documentation-only patch. - `git diff --check`: passed. Commands for the focused checks (with an additional local Maven repository override in this environment): ```sh mvn -B -pl seatunnel-transforms-v2,seatunnel-connectors-v2/connector-fake,seatunnel-connectors-v2/connector-console -am '-Dtest=FieldMapperTransformTest,FieldMapperTransformFactoryTest,AbstractMultiCatalogTransformTest,ConfigTest' -Dsurefire.failIfNoSpecifiedTests=false verify mvn -B -pl seatunnel-ci-tools -am -Dtest=MarkdownTest -Dsurefire.failIfNoSpecifiedTests=false test ``` Limitations: the Maven wrapper could not download its launcher in this environment, so the installed Maven was used. Root `mvn -q -DskipTests verify` was attempted but failed while resolving `org.apache.spark:spark-tags_2.12:pom:2.4.0` from the configured Aliyun mirror (HTTP 502). Full-repository verification and engine-cluster execution are therefore not claimed as passing. No production or test source files were changed. ### Check list - [x] English and Chinese documentation updated together. - [x] Configuration names, defaults and constraints checked against implementation. - [x] Complete job configurations and expected results included. - No new dependencies, binaries, connector registrations or compatibility changes. Prepared with Codex assistance; source behavior and examples were checked locally as described above. -- 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]
