We've been talking about this a little internally as well. What about the idea of presenting all the admin functions through a web API interface (restful or not) complete with authentication? That would make it much easier for creating structure around Kafka without having to layer commands on top of each other.
I'm not a big fan of the language specific interfaces, because they tend to complicate trying to integrate with larger systems. Consider something like AWS or Azure, where it would be much easier if there is an API interface like that. -Todd > On Oct 17, 2014, at 5:03 PM, Joe Stein <joe.st...@stealth.ly> wrote: > > Hi, I have been thinking about the ease of use for operations with Kafka. > We have lots of tools doing a lot of different things and they are all kind > of in different places. > > So, what I was thinking is to have a single interface for our tooling > https://issues.apache.org/jira/browse/KAFKA-1694 > > This would manifest itself in two ways 1) a command line interface 2) a repl > > We would have one entry point centrally for all Kafka commands. > kafka <CMD> <ARGS> > kafka createTopic --brokerList etc, > kafka reassignPartition --brokerList etc, > > or execute and run the shell > > kafka --brokerList localhost > kafka>use topicName; > kafka>set acl='label'; > > I was thinking that all calls would be initialized through --brokerList and > the broker can tell the KafkaCommandTool what server to connect to for > MetaData. > > Thoughts? Tomatoes? > > /******************************************* > Joe Stein > Founder, Principal Consultant > Big Data Open Source Security LLC > http://www.stealth.ly > Twitter: @allthingshadoop <http://www.twitter.com/allthingshadoop> > ********************************************/
