[ 
https://issues.apache.org/jira/browse/FLINK-35648?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17873110#comment-17873110
 ] 

Ruan Hang commented on FLINK-35648:
-----------------------------------

fix via master: 3441a1e2ab17f194bc27191819089153bf13d730

> 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
>    Affects Versions: cdc-3.1.1
>            Reporter: yux
>            Assignee: yux
>            Priority: Major
>              Labels: pull-request-available
>             Fix For: cdc-3.2.0
>
>
> 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)

Reply via email to