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

Posted to issues@flink.apache.org by "Ruan Hang (Jira)" <ji...@apache.org> on 2024/06/19 08:42:00 UTC

[jira] [Assigned] (FLINK-35648) Pipeline job doesn't support multiple routing

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

Ruan Hang reassigned FLINK-35648:
---------------------------------

    Assignee: yux

> Pipeline job doesn't support multiple routing
> ---------------------------------------------
>
>                 Key: FLINK-35648
>                 URL: https://issues.apache.org/jira/browse/FLINK-35648
>             Project: Flink
>          Issue Type: Improvement
>          Components: Flink CDC
>            Reporter: yux
>            Assignee: yux
>            Priority: Major
>
> Currently, any upstream could be routed at most once, which means if we wrote such route  definition:
> routes:
>   - source-table: db.(A|B)
>      sink-table: terminal.one
>   - source0table: db.(B|C)
>      sink-table: terminal.two
> Any upstream schema / data changes from db.B will be sent to terminal.one {*}only{*}, not to terminal.two since it has been handled by the first route rule.
> This ticket suggests adding a route behavior option (FIRST_MATCH / COMPLETE) to configure if all route rules should be applied or only the first matched rule (for backwards compatibility.).



--
This message was sent by Atlassian Jira
(v8.20.10#820010)