[
https://issues.apache.org/jira/browse/KAFKA-2350?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14638139#comment-14638139
]
Jay Kreps commented on KAFKA-2350:
----------------------------------
[~hachikuji] yeah i vote for pause/resume (or unpause).
I think the challenge with making group management explicit is that then it
will conflict with the api usage. I.e. the user will say
client.subscribe(mytopic) and something terrible and bad will happen and they
won't know why and we will say uh uh uh you forgot to set the magic
enable.consumer.coordinator=true flag. This was kind of what I liked about the
implicit approach--the natural usage of just subscribing to a partition or
topic does what you would expect. I would anticipate making this a flag turning
into a source of confusion because in the early stages of usage most people
won't know what a consumer coordinator is.
> Add KafkaConsumer pause capability
> ----------------------------------
>
> Key: KAFKA-2350
> URL: https://issues.apache.org/jira/browse/KAFKA-2350
> Project: Kafka
> Issue Type: Improvement
> Reporter: Jason Gustafson
> Assignee: Jason Gustafson
>
> There are some use cases in stream processing where it is helpful to be able
> to pause consumption of a topic. For example, when joining two topics, you
> may need to delay processing of one topic while you wait for the consumer of
> the other topic to catch up. The new consumer currently doesn't provide a
> nice way to do this. If you skip poll() or if you unsubscribe, then a
> rebalance will be triggered and your partitions will be reassigned.
> One way to achieve this would be to add two new methods to KafkaConsumer:
> {code}
> void pause(String... topics);
> void unpause(String... topics);
> {code}
> When a topic is paused, a call to KafkaConsumer.poll will not initiate any
> new fetches for that topic. After it is unpaused, fetches will begin again.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
