-
Enhancement
-
Resolution: Done
-
Major
-
None
-
None
-
False
-
None
-
False
In order to make your issue reports as actionable as possible, please provide the following information, depending on the issue type.
Bug report
For bug reports, provide this information, please:
What Debezium connector do you use and what version?
SQL Server 2.3.2.Final
What is the connector configuration?
{
"topic.prefix": "prefix",
"name": "test",
"database.names": "test",
"connector.class": "io.debezium.connector.sqlserver.SqlServerConnector", "database.hostname": "<redacted>",
"database.port": "1433",
"database.user": "<redacted>",
"database.password": "<redacted>",
"database.instance": "<redacted>",
"include.schema.changes": "true",
"database.dbname": "test",
"database.server.name": "test",
"database.trustServerCertificate": "true", "schema.history.internal.consumer.security.protocol": "SSL", "schema.history.internal.consumer.ssl.key.password": "<redacted>", "schema.history.internal.consumer.ssl.keystore.location": "<redacted>", "schema.history.internal.consumer.ssl.keystore.password": "<redacted>", "schema.history.internal.consumer.ssl.keystore.type": "PKCS12", "schema.history.internal.consumer.ssl.truststore.location": "<redacted>", "schema.history.internal.consumer.ssl.truststore.password": "<redacted>", "schema.history.internal.kafka.bootstrap.servers": "<redacted>", "schema.history.internal.kafka.topic": "history_topic", "schema.history.internal.producer.security.protocol": "SSL", "schema.history.internal.producer.ssl.key.password": "<redacted>", "schema.history.internal.producer.ssl.keystore.location": "<redacted>", "schema.history.internal.producer.ssl.keystore.password": "<redacted>", "schema.history.internal.producer.ssl.keystore.type": "PKCS12", "schema.history.internal.producer.ssl.truststore.location": "<redacted>", "schema.history.internal.producer.ssl.truststore.password": "<redacted>
}
What is the captured database version and mode of depoyment?
(E.g. on-premises, with a specific cloud provider, etc.)
Google Cloud SQL, SQL Server 2019 Standard
What behaviour do you expect?
The connector should be working and capture the changes properly
What behaviour do you see?
Initial schema snapshot is failing with an exception
ERROR [test4|task-0] Error during snapshot (io.debezium.relational.RelationalSnapshotChangeEventSource:170) com.microsoft.sqlserver.jdbc.SQLServerException: The TDS protocol stream is not valid. at com.microsoft.sqlserver.jdbc.SQLServerConnection.terminate(SQLServerConnection.java:3680) at com.microsoft.sqlserver.jdbc.SQLServerConnection.terminate(SQLServerConnection.java:3669) at com.microsoft.sqlserver.jdbc.SQLServerConnection.throwInvalidTDS(SQLServerConnection.java:3652) at com.microsoft.sqlserver.jdbc.TDSReader.throwInvalidTDS(IOBuffer.java:6804) at com.microsoft.sqlserver.jdbc.StreamColumns.processDataClassification(StreamColumns.java:309) at com.microsoft.sqlserver.jdbc.StreamColumns.setFromTDS(StreamColumns.java:231) at com.microsoft.sqlserver.jdbc.SQLServerResultSet$1CursorInitializer.onColMetaData(SQLServerResultSet.java:300) at com.microsoft.sqlserver.jdbc.TDSParser.parse(tdsparser.java:112) at com.microsoft.sqlserver.jdbc.TDSParser.parse(tdsparser.java:37) at com.microsoft.sqlserver.jdbc.SQLServerResultSet.<init>(SQLServerResultSet.java:413) at com.microsoft.sqlserver.jdbc.SQLServerStatement.getNextResult(SQLServerStatement.java:1686) at com.microsoft.sqlserver.jdbc.SQLServerStatement.doExecuteStatement(SQLServerStatement.java:907) at com.microsoft.sqlserver.jdbc.SQLServerStatement$StmtExecCmd.doExecute(SQLServerStatement.java:802) at com.microsoft.sqlserver.jdbc.TDSCommand.execute(IOBuffer.java:7730) at com.microsoft.sqlserver.jdbc.SQLServerConnection.executeCommand(SQLServerConnection.java:3786) at com.microsoft.sqlserver.jdbc.SQLServerStatement.executeCommand(SQLServerStatement.java:268) at com.microsoft.sqlserver.jdbc.SQLServerStatement.executeStatement(SQLServerStatement.java:242) at com.microsoft.sqlserver.jdbc.SQLServerStatement.executeQuery(SQLServerStatement.java:724) at io.debezium.connector.sqlserver.SqlServerSnapshotChangeEventSource.lockTablesForSchemaSnapshot(SqlServerSnapshotChangeEventSource.java:144) at io.debezium.relational.RelationalSnapshotChangeEventSource.doExecute(RelationalSnapshotChangeEventSource.java:128) at io.debezium.pipeline.source.AbstractSnapshotChangeEventSource.execute(AbstractSnapshotChangeEventSource.java:76) at io.debezium.pipeline.ChangeEventSourceCoordinator.doSnapshot(ChangeEventSourceCoordinator.java:186) at io.debezium.connector.sqlserver.SqlServerChangeEventSourceCoordinator.executeChangeEventSources(SqlServerChangeEventSourceCoordinator.java:84) at io.debezium.pipeline.ChangeEventSourceCoordinator.lambda$start$0(ChangeEventSourceCoordinator.java:118) at java.base/java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:539) at java.base/java.util.concurrent.FutureTask.run(FutureTask.java:264) at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1136) at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:635) at java.base/java.lang.Thread.run(Thread.java:833)
Do you see the same behaviour using the latest relesead Debezium version?
(Ideally, also verify with latest Alpha/Beta/CR version)
Yes
Do you have the connector logs, ideally from start till finish?
(You might be asked later to provide DEBUG/TRACE level log)
<Your answer>
How to reproduce the issue using our tutorial deployment?
Just add sensitivity classification to any of the captured columns using
add sensitivity classification to <column_name> with ( rank = <any rank>);
Feature request or enhancement
For feature requests or enhancements, provide this information, please:
Which use case/requirement will be addressed by the proposed feature?
Support of sensitivity classification.
Implementation ideas (optional)
Upgrade SQL Server JDBC connector.
- links to
-
RHEA-2024:129636
Red Hat build of Debezium 2.5.4 release
