docs: add multi-table transform capability boundary guide#10985
Draft
DanielLeens wants to merge 3 commits into
Draft
docs: add multi-table transform capability boundary guide#10985DanielLeens wants to merge 3 commits into
DanielLeens wants to merge 3 commits into
Conversation
Clarify exactly what SeaTunnel's multi-table transform supports and does not support: - TableMerge vs SQL JOIN distinction - Cross-source JOIN limitation and workarounds - Per-table transform configuration pattern (table_match_regex) - Common-fields TableMerge pattern - EtLT recommended architecture - Capability boundary reference table - FAQ covering wildcard transforms, SQL JOIN, unmatched tables, and dynamic table addition Closes apache#10979 (P0-5)
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
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
docs/en/transforms/multi-table-transform-and-join-boundary.md(EN)docs/zh/transforms/multi-table-transform-and-join-boundary.md(ZH)docs/sidebars.jsto include the new page aftertransform-multi-tableCoverage
TableMergevs SQL JOIN distinction with clear examplestable_match_regexTableMergepattern (shared schema fan-in)Closes #10979 (P0-5)