You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@seatunnel.apache.org by "davidzollo (via GitHub)" <gi...@apache.org> on 2026/06/10 07:53:26 UTC

[I] [Feature][Transform-V2][CDC] Add route evaluation mode for multi-table routing [seatunnel]

davidzollo opened a new issue, #11045:
URL: https://github.com/apache/seatunnel/issues/11045

   ## Background
   When multi-table CDC jobs use routing rules, different teams may expect different matching semantics. Some need all matching rules to apply, while others need evaluation to stop at the first match.
   
   Today SeaTunnel does not expose an explicit route evaluation mode for this case.
   
   ## Proposed change
   Add a route evaluation mode for CDC multi-table routing so users can choose between applying all matching rules and stopping at the first matching rule.
   
   ## Expected behavior
   - The default behavior stays backward compatible.
   - A new configuration option controls route rule evaluation mode.
   - Rule ordering semantics are documented clearly when first-match mode is used.
   
   ## Acceptance criteria
   - A multi-table CDC route can be configured to use either all-match or first-match semantics.
   - First-match mode respects user-defined rule order.
   - English and Chinese docs are updated with examples.
   - Add focused tests for both evaluation modes.
   
   ## Out of scope
   - Soft-delete conversion.
   - New source metadata fields.
   - Automatic sink table creation options.
   


-- 
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: commits-unsubscribe@seatunnel.apache.org.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org


Re: [I] [Feature][Transform-V2][CDC] Add configurable rule evaluation mode for multi-table transform matching [seatunnel]

Posted by "goutamadwant (via GitHub)" <gi...@apache.org>.
goutamadwant commented on issue #11045:
URL: https://github.com/apache/seatunnel/issues/11045#issuecomment-4677476886

   Hi @davidzollo as discussed over chat and having a list from you to get started - I would like to take this as my warm-up issue.
   
   I will first trace the current multi-table transform matching path and keep the first PR focused on the configurable evaluation mode only. Plan is to add focused tests for first-match vs apply-all behavior and update the docs/config example if needed.
   
   I can assign this to me and start working on it :)


-- 
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: commits-unsubscribe@seatunnel.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org


Re: [I] [Feature][Transform-V2][CDC] Add configurable rule evaluation mode for multi-table transform matching [seatunnel]

Posted by "davidzollo (via GitHub)" <gi...@apache.org>.
davidzollo closed issue #11045: [Feature][Transform-V2][CDC] Add configurable rule evaluation mode for multi-table transform matching
URL: https://github.com/apache/seatunnel/issues/11045


-- 
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: commits-unsubscribe@seatunnel.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org


Re: [I] [Feature][Transform-V2][CDC] Add configurable rule evaluation mode for multi-table transform matching [seatunnel]

Posted by "DanielLeens (via GitHub)" <gi...@apache.org>.
DanielLeens commented on issue #11045:
URL: https://github.com/apache/seatunnel/issues/11045#issuecomment-4688434717

   Thanks for taking this one.
   
   Your proposed scope is the right direction for a first slice, but one detail is worth keeping explicit before implementation: the current multi-table transform resolver is still based on exact `table_path` child config plus outer `table_match_regex` fallback. It is not yet a general multi-match rule engine.
   
   So for the first PR, please make the matching model very explicit:
   1. what kinds of child rules are allowed to match the same upstream table
   2. how `FIRST_MATCH` / `ALL_MATCH` interact with the current exact-table behavior
   3. how backward compatibility is preserved as the default
   
   Focused tests for default behavior, fallback behavior, and deterministic rule order will be important here.
   
   This looks like a good first slice for the issue. Looking forward to the PR.


-- 
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: commits-unsubscribe@seatunnel.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org