Hi, What do you plan to use the read-only REST interface for? Is there something what you cannot get through metrics interface? Otherwise it might be easier to just disable the REST interface (either in the code, or just on the platform level - e.g. in Kubernetes).
Also, I do not know what is the usual approach in Kafka ... but do we really have to rename the offset.storage.* options? The current names do not seem to have any collision with what you are adding and they would get "out of sync" with the other options used in connect (status.storage.* and config.storage.*). So it seems a bit unnecessary change to me. Jakub On Wed, May 16, 2018 at 10:10 PM Saulius Valatka <saulius...@gmail.com> wrote: > Hi, > > I'd like to start a discussion on the following KIP: > > https://cwiki.apache.org/confluence/display/KAFKA/KIP-304%3A+Connect+runtime+mode+improvements+for+container+platforms > > Basically the idea is to make it easier to run separate instances of Kafka > Connect hosting isolated connectors on container platforms such as Mesos or > Kubernetes. > > In particular it would be interesting to hear opinions about the proposed > read-only REST API mode, more specifically I'm concerned about the > possibility to implement it in distributed mode as it appears the framework > is using it internally ( > > https://github.com/apache/kafka/blob/trunk/connect/runtime/src/main/java/org/apache/kafka/connect/runtime/distributed/DistributedHerder.java#L1019 > ), > however this particular API method appears to be undocumented(?). > > Looking forward for your feedback. >
