[
https://issues.apache.org/jira/browse/FLINK-38831?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18049116#comment-18049116
]
SkylerLin commented on FLINK-38831:
-----------------------------------
*current format is:*
route:
- source-table: ...
sink-table: ...
- source-table: ...
sink-table: ...
*If we want to add match-mode option, there are two choices:*
*option 1 is :*
route:
match-mode: first-match
rules:
- source-table: ...
sink-table: ...
- source-table: ...
sink-table: ...
*option 2 is :*
route:
- source-table: ...
sink-table: ...
- source-table: ...
sink-table: ...
route-mode: first-match
*Which one do you think is better? Or are there any other better options?
[~yux]*
> The route configuration supports matching the first one
> -------------------------------------------------------
>
> Key: FLINK-38831
> URL: https://issues.apache.org/jira/browse/FLINK-38831
> Project: Flink
> Issue Type: Improvement
> Components: Flink CDC
> Affects Versions: cdc-3.5.0
> Reporter: peiyu
> Assignee: SkylerLin
> Priority: Major
> Attachments: image-2025-12-23-15-10-21-540.png
>
>
> In scenarios involving full database synchronization, some tables are sharded
> while others are not. The desired outcome is that sharded tables are merged,
> while other tables maintain a one-to-one relationship. The current routing
> configuration rules are extremely cumbersome. We would like to support
> matching strategies similar to those in the `transform` module.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
