Is there any reason 'ConsumerConnector' being deprecated?

[Sunghyuk Gong]

I'm using kafka 0.8.2.1. and planning to upgrade to 1.0.0.

While doing upgrade, I noticed that these apis are deprecated or going to be deprecated as soon.

kafka.consumer.Consumer

kafka.javaapi.consumer.ConsumerConnector

kafka.javaapi.consumer.ZookeeperConsumerConnector

I can understand that consumer will be replaced with KafkaConsumer, which has same functionality.

But in case of ConsumerConnector, ZookeeperConsumerConnector, these are very useful because these objects connect topic(partition) to consumer automatically.

It was core functionality of our application, but I don't know what can I do when these are deprecated.

Should I develop other function or library to replace these objects on my own? or is there other way to implement these objects?

[Manikumar]

>>"But in case of ConsumerConnector, ZookeeperConsumerConnector, these are very useful because these objects connect topic(partition) to consumer automatically."

 

   Not understood, why you can not use KafkaConsumer in place of ZookeeperConsumerConnector? 

   All old consumer functionality can be implemented by using KafkaConsumer. 

      

--
You received this message because you are subscribed to the Google Groups "kafka-clients" group.
To unsubscribe from this group and stop receiving emails from it, send an email to kafka-clients+unsubscribe@googlegroups.com.
To post to this group, send email to kafka-...@googlegroups.com.
Visit this group at https://groups.google.com/group/kafka-clients.
To view this discussion on the web visit https://groups.google.com/d/msgid/kafka-clients/4c7dbcb0-9a05-44b5-8913-452008b2e598%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Sunghyuk Gong]

I think I didn't fully describe how I using ZookeeperConsumerConnector.

as a constructor, ZookeeperConsumerConnector takes map which key is topic and value is # of consumers.

and it create consumer and take stream from broker automatically.

so when I call createMessageStreams of ZookeeperConsumerConnector, it just returns map of topic and KafkaStream.

the point that I think it was useful was this.

If KafkaConsumer supports same or similar functionality and I didn't know, I will do more study about it.

thanks for reply!

2018년 2월 2일 금요일 오후 4시 27분 39초 UTC+9, ManiKumar Reddy 님의 말:

>>"But in case of ConsumerConnector, ZookeeperConsumerConnector, these are very useful because these objects connect topic(partition) to consumer automatically."

 

   Not understood, why you can not use KafkaConsumer in place of ZookeeperConsumerConnector? 

   All old consumer functionality can be implemented by using KafkaConsumer. 

      

On Fri, Feb 2, 2018 at 12:51 PM, Sunghyuk Gong <gong....@gmail.com> wrote:

I'm using kafka 0.8.2.1. and planning to upgrade to 1.0.0.

While doing upgrade, I noticed that these apis are deprecated or going to be deprecated as soon.

kafka.consumer.Consumer

kafka.javaapi.consumer.ConsumerConnector

kafka.javaapi.consumer.ZookeeperConsumerConnector

I can understand that consumer will be replaced with KafkaConsumer, which has same functionality.

But in case of ConsumerConnector, ZookeeperConsumerConnector, these are very useful because these objects connect topic(partition) to consumer automatically.

It was core functionality of our application, but I don't know what can I do when these are deprecated.

Should I develop other function or library to replace these objects on my own? or is there other way to implement these objects?

--
You received this message because you are subscribed to the Google Groups "kafka-clients" group.

To unsubscribe from this group and stop receiving emails from it, send an email to kafka-client...@googlegroups.com.