-
Notifications
You must be signed in to change notification settings - Fork 1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Feature][cdc] Handle Kafka CDC Debezium/Canal JSON from Flink SQL #2706
Comments
I have the same problem.First, I use mysqlcdc to kafka topic. Then I use kafka cdc action to paimon.I found that the table that automatically builds paimon does not correctly identify the primary key. the record in topic like that:
the id column is my table primary key. |
@Pandas886 In your case, maybe you can specify --primary_key ? |
the topic has all tables in a database. |
Search before asking
Motivation
At present, some Kafka CDC data comes from Flink SQL, and the CDC data produced by Flink SQL lacks a lot of information (even the data from Flink CDC lacks PK information). There is no schema or PK, and we should also have the ability to handle such scenarios in our Paimon Kafka CDC.
Solution
No response
Anything else?
No response
Are you willing to submit a PR?
The text was updated successfully, but these errors were encountered: