tag for connect-standalone

[streamsend-io]

This is a great container and works well - thank you. A slimmer container creates a stonger use case for "connect at the edge" - since the smaller footprint enables source connectors to stream from edge locations. These containers are unlikely to run in connect-distributed mode; instead they would run in connect-standalone mode.

A connect-standalone tag would

• add property CONNECT_OFFSET_STORAGE_FILE_FILENAME
• remove properties CONNECT_OFFSET_STORAGE_TOPIC, CONNECT_CONFIG_STORAGE_TOPIC, CONNECT_STATUS_STORAGE_TOPIC
• change the EntryPoint from org.apache.kafka.connect.cli.ConnectDistributedWrapper to org.apache.kafka.connect.cli.ConnectStandaloneWrapper.

[OneCricketeer]

Thanks for the request. Can you clarify how changing the entrypoint would create a slimmer container? All the runtime Java classes would still be there. Connect standalone still runs a jetty server.

[streamsend-io]

Hi,
Clarification: I am acknowlodging that this container is slimmer than cp-connect. Adding a tag capability for connectStandalone would not impact the container size, AFAIK.

Changing the endpoint to use "org.apache.kafka.connect.cli.ConnectStandaloneWrapper"
returns ERROR " Could not find or load main class org.apache.kafka.connect.cli.ConnectStandaloneWrapper"
I'm unfamiliar with "ConnectDistributedWrapper" - where is this defined?

[OneCricketeer]

Changing the entrypoint to that isn't possible, since that class doesn't exist.

https://github.com/OneCricketeer/apache-kafka-connect-docker/blob/master/src/main/java/org/apache/kafka/connect/cli/ConnectDistributedWrapper.java