CodyPin commented on issue #3308: URL: https://github.com/apache/paimon/issues/3308#issuecomment-2102317357
On futher investigation, using the query `show KEYS from <tablename> where Key_name = 'PRIMARY';` on the tables that got included, namely `user` and `sku_list` shows this   But on those who got filtered out, for example `store` and `payment_record`, it reutrns nothing:   Even tho when we query `describe store` shows that the table does indeed have a primary key:  Turns out, when the tables were created, it didn't specify the primary key, but was instead later added using the query `ALTER TABLE store ADD PRIMARY KEY (id); `. This leads to the problem that it might appears that the table does not have a primary key, like when using the query `show create table store;` will show this:  showing that it does not have a primary key. With that said, althought the tables clearly have a primary key, it might appares as it does not depending on how we are checking for its existence, and of course [Paimon only synchronizes tables with primary keys](https://paimon.apache.org/docs/master/flink/cdc-ingestion/mysql-cdc/#synchronizing-databases). So I think this is a bug in the wording of the documents, but would be a really nice feature if it would include tables that have a primary no matter if its created with or altered later on. @MOBIN-F what do you think? -- 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: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
