This page is meant as a template for writing a KIP. To create a KIP choose Tools->Copy on this page and modify with your content and replace the heading with the next KIP number and a description of your issue. Replace anything in italics with your own description.
Status
Current state: "Under Discussion"
Discussion thread: https://lists.apache.org/thread.html/r6d5b70da58fd7c81648cba5bfd773fa615ecb52fe61b05412dc8b092%40%3Cdev.kafka.apache.org%3E
JIRA:
Please keep the discussion on the mailing list rather than commenting on the wiki (wiki discussions get unwieldy fast).
Motivation
When starting Kafka with its server.properties file, one can override some properties using the --override option. In contrast, when starting Kafka-Connect with its worker.properties file, there is no --override option.
Having the --override option when starting Kafka-Connect will provide the users the flexibility in starting Kafka-Connect in various situations. While lacking of this option is confusing for those users who have used the --override option for Kafka.
Public Interfaces
A new option is added for connect-distributed.sh
--override <String>: Optional property that should override values set in worker.properties file
Proposed Changes
We proposed to add the handling of the --override arguments at DistributedConnect. It appears that only a minor change is required at the startup of DistributedConnect and the proposed change is available at https://github.com/elakito/kafka/tree/ay-connect-cmdopts with commit https://github.com/elakito/kafka/commit/1e54536598d1ce328d0aee10edb728270cc04af1
Compatibility, Deprecation, and Migration Plan
- no impact on existing users
- compatible with the older behavior, no migration needed