Thanks, Ewen :) One thing that wasn't clear to me from the wiki: Will standalone connect also have a Kafka cluster ID? While it is true that only tasks have producers and consumers, I think we assumed that all tasks on one stand-alone will use one Kafka cluster?
Another suggestion is not to block the REST API on the connection, but rather not return the cluster ID until we know it (return null instead). So clients will need to poll rather than block. Not sure this is better, but you didn't really discuss this, so wanted to raise the option. Gwen On Mon, Dec 11, 2017 at 3:42 PM Ewen Cheslack-Postava <e...@confluent.io> wrote: > I'd like to start discussion on a simple KIP to expose Kafka cluster ID > info in the Connect REST API: > > > https://cwiki.apache.org/confluence/display/KAFKA/KIP-238%3A+Expose+Kafka+cluster+ID+in+Connect+REST+API > > Hopefully straightforward, though there are some details on how this > affects startup behavior that might warrant discussion. > > -Ewen >
