Skip to content

[hotfix][mysql] Correct the use of includeSchemaChanges parameter #501

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.

Sign up for GitHub

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

Merged
merged 1 commit into from
Oct 15, 2021
Merged

[hotfix][mysql] Correct the use of includeSchemaChanges parameter #501

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
5 changes: 4 additions & 1 deletion .../main/java/com/ververica/cdc/connectors/mysql/source/config/MySqlSourceConfigFactory.java
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -200,7 +200,10 @@ public MySqlSourceConfig createConfig(int subtaskId) {
props.setProperty("database.history.skip.unparseable.ddl", String.valueOf(true));
props.setProperty("database.history.refer.ddl", String.valueOf(true));
props.setProperty("connect.timeout.ms", String.valueOf(connectTimeout.toMillis()));
props.setProperty("include.schema.changes", String.valueOf(includeSchemaChanges));
// the underlying debezium reader should always capture the schema changes and forward them.
// Note: the includeSchemaChanges parameter is used to controll emitting the schema record,
// only DataStream API program need to emit the schema record, the Table API need not
props.setProperty("include.schema.changes", String.valueOf(true));
// disable the offset flush totally
props.setProperty("offset.flush.interval.ms", String.valueOf(Long.MAX_VALUE));
// disable tombstones
Expand Down