We plan to, but there is quite a bit of functionality that needs to be abstracted by requests to the broker. Most of the functionality in the topics command that interacts directly with ZK will be replaced by KIP-4 protocols ( https://cwiki.apache.org/confluence/display/KAFKA/KIP-4+-+Command+line+and+centralized+administrative+operations) and gradually transitioned over. Just as with the new clients, this implementation and transition will take some time.
-Ewen On Mon, Jan 23, 2017 at 10:37 PM, Stephane Maarek < steph...@simplemachines.com.au> wrote: > Hi Ewen > > If the trend is to hide zookeeper entirely (and most likely restricting its > network connection to Kafka only ) would it make sense to update the Kafka > topics tool ? Currently it is > > > *bin/kafka-topics.sh --create --zookeeper localhost:2181 > --replication-factor 1 --partitions 1 --topic test* > > > On 24 Jan. 2017 3:25 pm, "Ewen Cheslack-Postava" <e...@confluent.io> > wrote: > > > The new consumer only supports committing offsets to Kafka. (It doesn't > > even have connection info to ZooKeeper, which is a general trend in Kafka > > clients -- all details of ZooKeeper are being hidden away from clients, > > even administrative functions like creating topics.) > > > > -Ewen > > > > On Thu, Jan 19, 2017 at 7:00 PM, vinay ng <vinay.ng....@gmail.com> > wrote: > > > > > Hi, > > > > > > As per Kafka documentation, > > > > > > *Automatic Offset Committing,* > > > "Setting enable.auto.commit means that offsets are committed > > > automatically." > > > > > > Can you help me understand where the offsets are stored in case of > > > automatic offset committing.. I believe it used to be on Zookeeper but > > not > > > anymore as per new KafkaConsumer API. > > > > > > > > > Thanks > > > > > >
