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

Debezium server with eventhubs sink type and eventhubs emulator connection string fails

XMLWordPrintable

    • Moderate

      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?

      Connector: Debezium Server with Azure Eventhubs sink type
      2.7.3.Final and 3.0.1.Final

      What is the connector configuration?

       

       debezium-server-eventhubs-emulator:
          container_name: "debezium-sqlserver"
          image: quay.io/debezium/server:${DEBEZIUM_VERSION}
          ports:
            - "8080:8080"
          environment:
            DEBEZIUM_SOURCE_CONNECTOR_CLASS: "io.debezium.connector.sqlserver.SqlServerConnector"
            DEBEZIUM_SOURCE_SNAPSHOT_ISOLATION_MODE: read_uncommitted
            DEBEZIUM_SOURCE_TOPIC_PREFIX: ${EVENT_HUB_NAME}
            DEBEZIUM_SOURCE_OFFSET_STORAGE_FILE_FILENAME: "./data/offsets.dat"
            DEBEZIUM_SOURCE_SCHEMA_HISTORY_INTERNAL: "io.debezium.storage.file.history.FileSchemaHistory"
            DEBEZIUM_SOURCE_SCHEMA_HISTORY_INTERNAL_FILE_FILENAME: "./data/schema_history_internal.dat"
            DEBEZIUM_SOURCE_DATABASE_HOSTNAME: sqlserver
            DEBEZIUM_SOURCE_DATABASE_ENCRYPT: false
            DEBEZIUM_SOURCE_DATABASE_PORT: 1433
            DEBEZIUM_SOURCE_DATABASE_NAMES: testDB
            DEBEZIUM_SOURCE_DATABASE_USER: sa
            DEBEZIUM_SOURCE_DATABASE_PASSWORD: $MSSQL_PASSWORD
            DEBEZIUM_SINK_TYPE: eventhubs
            DEBEZIUM_SINK_EVENTHUBS_CONNECTIONSTRING: ${EVENT_HUB_CONNECTION_STRING}
            DEBEZIUM_SINK_EVENTHUBS_HUBNAME: ${EVENT_HUB_NAME}
            QUARKUS_LOG_LEVEL: DEBUG
            QUARKUS_LOG_CONSOLE_JSON: false
          volumes:
            - $PWD/data:/data \
          networks:
            test-network:
              aliases:
                - "debezium-server"
      networks:
        test-network:
      

       

       

      What is the captured database version and mode of deployment?

      (E.g. on-premises, with a specific cloud provider, etc.)

      Local development environment

      What behavior do you expect?

      Connection to the eventhub emulator (running in docker container) is established.

      What behavior do you see?

       

      2024-10-28T13:05:46.567624250Z Caused by: io.debezium.DebeziumException: java.lang.IllegalArgumentException: Illegal connection string parameter name: UseDevelopmentEmulator

       

      Do you see the same behaviour using the latest released 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)

      debug-level.log

       

       

      How to reproduce the issue using our tutorial deployment?

      1. Up the Azure event hubs emulator, e.g. via docker compose: azure-event-hubs-emulator
      2. Up a debezium server instance in docker container with some SQL source and EventHub sink.  

      You may use the docker compose script in the attachement compose.yaml and provide values for the environment variables (e.g via .env file)

      DEBEZIUM_VERSION=3.0.1.Final
      MSSQL_PASSWORD=SomeP@ssword!^
      SQL_SERVER_VERSION=2019-latest
      EVENT_HUB_CONNECTION_STRING=Endpoint=sb://localhost;SharedAccessKeyName=RootManageSharedAccessKey;SharedAccessKey=SAS_KEY_VALUE;UseDevelopmentEmulator=true;EntityPath=eh1
      EVENT_HUB_NAME=eh1

       

      Feature request or enhancement

      For feature requests or enhancements, provide this information, please:

      Which use case/requirement will be addressed by the proposed feature?

      Developers experience.

      Implementation ideas (optional)

      Increasing version of the azure-messaging-eventhubs dependency up to 
      5.18.5 fixes the issue 

        1. compose.yaml
          3 kB
          Farrukhjon Sattorov
        2. config.json
          0.4 kB
          Farrukhjon Sattorov
        3. debug-level.log
          103 kB
          Farrukhjon Sattorov

            ccranfor@redhat.com Chris Cranford
            farrukhjonsattorov Farrukhjon Sattorov
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated:
              Resolved: