Uploaded image for project: 'AMQ Streams'
  1. AMQ Streams
  2. ENTMQST-1481

Use `admin.` configuration prefix in Kafka Connect configuration

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Done
    • Icon: Major Major
    • 1.4.0.GA
    • 1.0.0.Beta on OCP, 1.0.0.OCP.GA, 1.0.1.GA, 1.1.0.GA, 1.1.1.GA, 1.2.0.GA, 1.3.0.GA, 1.4.0.GA
    • docker-images
    • None
    • 0
    • 2019.13, 2019.14

      Kafka Connect is currently configured in following way:

      • Without prefix for AdminClient used by KafkaConnect it self
      • Producer prefix
      • Consumer prefix
        However, there seems to be the admin. prefix missing whihc is used by some topics created by connectors. For example the dead letter queue topic. The issue can be reproduced for example by deploying the following connector:
      curl -X POST -H "Content-Type: application/json" --data '{ "name": "sink-test", "config": { "connector.class": "FileStreamSink", "tasks.max": "3", "topics": "kafka-test-apps", "file": "/tmp/test.sink.txt", "errors.deadletterqueue.topic.replication.factor": 1, "errors.deadletterqueue.topic.name": "dlq-es-sink",
      "errors.deadletterqueue.context.headers.enable": true } }' http://localhost:8083/connectors
      

      Which will crash the connect and in the log you can see that it is trying to authenticate without the correct authentication. This PR should fix it by adding the admin. prefix to the configuration file and using it with the regular configuration for authentication.

            morsak Maros Orsak
            scholzj JAkub Scholz
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated:
              Resolved: