You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@flink.apache.org by "ASF GitHub Bot (Jira)" <ji...@apache.org> on 2026/01/05 12:47:00 UTC

[jira] [Updated] (FLINK-38831) The route configuration supports matching the first one

     [ https://issues.apache.org/jira/browse/FLINK-38831?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

ASF GitHub Bot updated FLINK-38831:
-----------------------------------
    Labels: pull-request-available  (was: )

> 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
>              Labels: pull-request-available
>         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)