[PR] [FLINK-35323][runtime] Fix transform failure when one rule matches multiple tables with incompatible schema [flink-cdc]

[via GitHub]

yuxiqian opened a new pull request, #3313:
URL: https://github.com/apache/flink-cdc/pull/3313

   This closes [FLINK-35323](https://issues.apache.org/jira/browse/FLINK-35323).
   
   Currently, Transform module doesn’t support handling multiple tables with 
different schema within one projection / filtering rule. A minimum reproducible 
example is:
   
   ```yaml
   transform:
     - source-table: DB.TABLE\.*
       projection: \*
   ```
   
   If there are `DB.TABLE1` and `DB.TABLE2` in upstream source but with 
different schema, transform operator will panic.


-- 
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