Uploaded image for project: 'Debezium'
  1. Debezium
  2. DBZ-6739

2.3.1.Final SqlServer regression - query.fetch.size is defined twice

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Duplicate
    • Icon: Major Major
    • None
    • 2.3.1.Final
    • sqlserver-connector
    • None
    • False
    • None
    • False

      Bug report

      After upgrading from 2.3.0.Final to 2.3.1.Final my Debezium Engine SqlServer integration test fails with:

      org.apache.kafka.common.config.ConfigException: Configuration query.fetch.size is defined twice.

       

      What Debezium connector do you use and what version?

      debezium-connector-sqlserver-2.3.1.Final

      What is the connector configuration?

      Below are the user configurations:

      transforms=unwrap transforms.unwrap.type=io.debezium.transforms.ExtractNewRecordState transforms.unwrap.drop.tombstones=false transforms.unwrap.delete.handling.mode=rewrite transforms.unwrap.add.fields=name,db,op,table schema.history.internal=io.debezium.relational.history.MemorySchemaHistory offset.storage=org.apache.kafka.connect.storage.MemoryOffsetBackingStore schema=false topic.prefix=my-topic name=my-connector database.server.id=85744
      
      connector.class=io.debezium.connector.sqlserver.SqlServerConnector database.user=... database.password=... database.encrypt=false database.names=testDB database.hostname=localhost database.port=1433  

       
      Note: I'm NOT setting the  query.fetch.size explicitly.

      What is the captured database version and mode of depoyment?

      My integration tests use an cdc instrumented image:

      mcr.microsoft.com/mssql/server:2022-latest

       

      It is working fine with sqlconnector 2.3.0.Final

      What behaviour do you expect?

      Expect the sql connector to successfully connect to my SqlServer instance as it did with 2.3.0.Final

      What behaviour do you see?

      I see this error:

      org.apache.kafka.common.config.ConfigException: Configuration query.fetch.size is defined twice.

       

      Do you see the same behaviour using the latest relesead Debezium version?

      (Ideally, also verify with latest Alpha/Beta/CR version)

      It works with 2.3.0.Final but failed with 2.3.1.Final

      It is likely that the regression is due to this commit: 
      https://github.com/debezium/debezium/commit/d3ad2bf318c9bc3188171ba4638759f18c9ef847#diff-eb175c0416ed060a1a98046c5daeb07d397d7d009833629c3f7e11b5e6651f28R318

      Do you have the connector logs, ideally from start till finish?

      (You might be asked later to provide DEBUG/TRACE level log)

      I don't

      How to reproduce the issue using our tutorial deployment?

      Here is my integration test:

      To reproduce you need to: checkout the https://github.com/tzolov/stream-applications repository, switch to the debezium-231 branch, run ./mvnw clean install -DskipTests at the root build all projects. Then you can run the DebeziumDatabasesIntegrationTest.java#L157

       

              Unassigned Unassigned
              christian.tzolov Christian Tzolov (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

                Created:
                Updated:
                Resolved: