DanielLeens opened a new pull request, #10985: URL: https://github.com/apache/seatunnel/pull/10985
## Purpose Clarify exactly what SeaTunnel's multi-table transform layer supports and does not support. This is a common source of user confusion and support questions. ## Changes - Added `docs/en/transforms/multi-table-transform-and-join-boundary.md` (EN) - Added `docs/zh/transforms/multi-table-transform-and-join-boundary.md` (ZH) - Updated `docs/sidebars.js` to include the new page after `transform-multi-table` ## Coverage - Capability boundary reference table (supported / not supported / partial) - `TableMerge` vs SQL JOIN distinction with clear examples - Cross-source JOIN limitations and recommended alternatives - Per-table transform configuration pattern using `table_match_regex` - Common-fields `TableMerge` pattern (shared schema fan-in) - EtLT recommended architecture: light transforms in SeaTunnel, heavy transforms downstream - FAQ: wildcard transforms, SQL JOIN, unmatched table fate, dynamic table addition Closes #10979 (P0-5) -- 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]
