Skip to content
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

When consuming Alibaba Cloud PolarDB, there is one more column than the fields in the table. #883

Open
chaotianque opened this issue May 24, 2024 · 3 comments

Comments

@chaotianque
Copy link

CREATE TABLE test1 (
id bigint(20) NOT NULL COMMENT '主键ID',
bill_type tinyint(2) NOT NULL DEFAULT '1' COMMENT '',
collect_no varchar(32) NOT NULL DEFAULT '' COMMENT '',
create_time timestamp NULL DEFAULT NULL COMMENT '',
PRIMARY KEY (id) USING BTREE,
KEY f_idx_bgt ((cast(create_time as date)))
) ENGINE=InnoDB

KEY f_idx_bgt ((cast(create_time as date)))
After testing, this index is recognized as a column

I used 1.7 and 1.8

@chaotianque
Copy link
Author

com.zendesk mysql-binlog-connector-java 0.29.1
I use this to subscribe to binlog and the columns that appear are normal.

UpdateRowsEventData: UpdateRowsEventData{tableId=11071, includedColumnsBeforeUpdate={0, 1, 2, 3}, includedColumns={0, 1, 2, 3}, rows=[

{before=[21, 2, 2211, null], after=[21, 2, 22111, null]}
]}

@chaotianque
Copy link
Author

企业微信截图_20240524094234
This is subscribed by go-mysql

@lance6716
Copy link
Collaborator

duplicated with #882

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants