[
https://issues.apache.org/jira/browse/FLINK-37673?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17944538#comment-17944538
]
MOBIN commented on FLINK-37673:
-------------------------------
It seems to be related to this
[PR|https://github.com/apache/flink-cdc/pull/3865] that this transform should
throw [different column counts] exceptions [~kunni]
> The transformation of table metadata should only be effective for the first
> matching rule
> ------------------------------------------------------------------------------------------
>
> Key: FLINK-37673
> URL: https://issues.apache.org/jira/browse/FLINK-37673
> Project: Flink
> Issue Type: Bug
> Components: Flink CDC
> Affects Versions: cdc-3.4.0
> Reporter: Yanquan Lv
> Priority: Major
>
> Considering a scenario where we have two transform rules, If there is a table
> that satisfies both of these matching rules, Only the first matching rule
> should take effect.
> However for primary keys and partition keys, this is currently the last rule
> to take effect now.
> //======================
> How to product：
> {code:java}
> transform:
> - source-table: mydb.web_order
> projection: id, order_id, UPPER(product_name) as product_name
> partition-keys: product_name
> - source-table: mydb.web_order
> projection: id, order_id, UPPER(product_name) as product_name, name
> partition-keys: id, product_name {code}
> mydb.web_order will be created with column of id, order_id, product_name,
> name and partition column of id, product_name.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
