You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I had searched in the issues and found no similar optimization requirement.
Description
After the flink cdc released the new version 3.1, the whole project was developed under apache scope and package names all changed;If u integrate the latest flink cdc into dinky, the version conflict will happen, because the jar depandency and class import could not be found
The pom xml still contain the flink cdc package from ververica
The cdc class still be imported from ververica
We hope dinky from 1.1 could catch up with the latest flink cdc!
medivh511
changed the title
[Optimization][dinky-cdc] Solve the dinky cdc integration issue after flink cdc upgrade from 3.1
[Optimization][dinky-cdc] Solve the dinky cdc integration issue after flink cdc upgraded from 3.1
Jun 20, 2024
medivh511
changed the title
[Optimization][dinky-cdc] Solve the dinky cdc integration issue after flink cdc upgraded from 3.1
[Optimization][dinky-cdc] Suggest to fix the dinky cdc integration issue after flink cdc upgraded from 3.1
Jun 23, 2024
Search before asking
Description
After the flink cdc released the new version 3.1, the whole project was developed under apache scope and package names all changed;If u integrate the latest flink cdc into dinky, the version conflict will happen, because the jar depandency and class import could not be found
We hope dinky from 1.1 could catch up with the latest flink cdc!
Are you willing to submit a PR?
Code of Conduct
The text was updated successfully, but these errors were encountered: