lvyanquan commented on PR #3865:
URL: https://github.com/apache/flink-cdc/pull/3865#issuecomment-2818203231
Thanks for your fix.
But there is now a user scenario where users want to add fields of
`__namespace_name__ || '.' || __schema_name__ || '.' || __table_name__
identifier_name` and `__data_event_type__ AS op_type` to certain tables, but
they do not need these two fields for other tables(or only one
`__data_event_type__ AS op_type` field). and their yaml file may looks like
this:
```
transform:
- source-table: mydb.web_order[0-9]+
projection: id, order_id, __namespace_name__ || '.' || __schema_name__
|| '.' || __table_name__ identifier_name, __data_event_type__ AS op_type
- source-table: \.*.\.*
projection: \*, __data_event_type__ AS op_type
```
Because we do not have table.exclude configuration in transform, making it
difficult to configure such information for other tables if we require the same
schema after each transform rule.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: issues-unsubscr...@flink.apache.org
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
