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

Debezium Server 1.9.6 is using MSSQL JDBC 7.2.2 instead of 9.4.1

    XMLWordPrintable

Details

    • False
    • None
    • False
    • Hide
      1. Download the distributable from here
      2. Open debezium/lib folder
      3. Check the MSSQL JDBC driver version which is 7.2.2 instead of 9.4.1
      Show
      Download the distributable from here Open debezium/lib folder Check the MSSQL JDBC driver version which is 7.2.2 instead of 9.4.1

    Description

      Debezium Server 1.9.6 has an old version of the MSSQL driver 7.2.2 (mssql-jdbc-7.2.2.jre8.jar) in the debezium/lib/ folder. Whereas on the releases page it says that Debezium 1.9.6 was tested with a newer version of the driver 9.4.1.jre8.

      Based on this coversation it looks like "there is a dependency conflict at debezium-server-dist module and that Quarkus version is used instead of Debezium's"

      Bug report

      What Debezium connector do you use and what version?

      I'm using Debezium Server 1.9.6

      What is the connector configuration?

      N/A

      What is the captured database version and mode of depoyment?

      N/A

      What behaviour do you expect?

      I expect to see a new version of the MSSQL Driver 9.4.1 in the debezium/lib/ folder.

      What behaviour do you see?

      debezium/lib/ folder contains mssql-jdbc-7.2.2.jre8.jar.

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

      Checked only on Debezium Server 1.9.6.Final.

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

      N/A

      How to reproduce the issue using our tutorial deployment?

      N/A

      Attachments

        Activity

          People

            jpechane Jiri Pechanec
            artsemi.dzmitryieu Artsemi Dzmitryieu (Inactive)
            Votes:
            1 Vote for this issue
            Watchers:
            5 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: