Chris Egerton created KAFKA-13731:
-------------------------------------
Summary: Standalone Connect workers should not require connector
configs to start
Key: KAFKA-13731
URL: https://issues.apache.org/jira/browse/KAFKA-13731
Project: Kafka
Issue Type: Improvement
Components: KafkaConnect
Reporter: Chris Egerton
Assignee: Chris Egerton
In order to start a standalone Connect worker, it's currently necessary to
provide at least two command-line arguments:
# The path to the worker config file
# One or more paths to a connector config file
This may be due to the now-inaccurate belief that standalone workers do not
support the Connect REST API, which can be used to create/reconfigure/delete
connectors at runtime. However, standalone mode does in fact expose the Connect
REST API, and since that allows for connectors to be created after bringing up
the worker, it is unnecessary to force users to supply at least one config for
a connector to be run on the worker at startup time.
We should remove the requirement that at least one connector config file be
provided to standalone Connect workers at startup time. This has several
benefits:
# Easier to debug for developers investigating framework behavior, including
potential bugs
# Easier to experiment against for developers/developer evangelists who want
to write quickstarts that leverage standalone mode
# Allows for connector config files to be tracked exclusively in JSON format
(the REST API uses JSON for connector configs, whereas the configs passed to
standalone workers on startup have to be Java properties files)
# Helps avoid perpetuating the unfortunately common myth that standalone
workers do not expose a rest API
# Allows for standalone workers to be brought up even if there are issues with
connector configs (if there are validation or startup issues with connector
configs provided on the command line, the worker will fail to start up)
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
