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: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
