Skip to content

Conversation

@naveenmall11
Copy link
Member

@naveenmall11 naveenmall11 commented Jan 17, 2026

Remove redundant calls for refresh schema
Upstream ticket: https://issues.redhat.com/browse/DBZ-8595
Upstream fix: debezium#6194

https://confluent.slack.com/archives/C0A83JB5UMR/p1768578389214619
Upstream fix: debezium#7022

@naveenmall11 naveenmall11 requested a review from a team as a code owner January 17, 2026 05:44
final MongoDbSnapshotContext mongoDbSnapshotContext = (MongoDbSnapshotContext) snapshotContext;

LOGGER.info("Snapshot step 1 - Preparing");
LOGGER.info("Logging here to know image build was successful")

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

we don't need this log anymore

}

LOGGER.info("Starting streaming");
LOGGER.info("Logging for validation");

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

we don't need this as well

Copy link
Member

@akanimesh7 akanimesh7 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@naveenmall11 Are we going ahead with test logs ?

@@ -142,7 +141,6 @@ protected void lockTablesForSchemaSnapshot(ChangeEventSourceContext sourceContex
LOGGER.info("Waiting a maximum of '{}' seconds for each table lock", lockTimeout.getSeconds());
jdbcConnection.executeWithoutCommitting(statements.toString());
// now that we have the locks, refresh the schema
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Remove the comment too

stream.startKeepAlive(
Threads.newSingleThreadExecutor(PostgresConnector.class, connectorConfig.getLogicalName(), KEEP_ALIVE_THREAD_NAME, threadNameContext));

initSchema();
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@yashisrivastava-confluent For my understanding, init schema before starting streaming is not required, because streaming starts exactly from the point noted during snapshot. Is it ?

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

yes

@yashisrivastava-confluent yashisrivastava-confluent merged commit f3170e3 into v3.0.8-hotfix-x Jan 28, 2026
1 of 2 checks passed
@yashisrivastava-confluent yashisrivastava-confluent deleted the schema-refresh-fix branch January 28, 2026 11:07
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

Successfully merging this pull request may close these issues.

4 participants