[
https://issues.apache.org/jira/browse/KAFKA-2350?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14637317#comment-14637317
]
Jay Kreps commented on KAFKA-2350:
----------------------------------
[~hachikuji] Yeah I agree that would help this case. The nice thing about that
proposal is it would make the group management explicit which could be nice. I
wonder if that might not add more things that can go wrong in the common case,
though. i.e. right now the common case of just subscribing to a topic and
letting the group management figure out the assignment and it is kind of hard
to mess that up. All the cases where either you subscribe to individual
partitions or you pause partitions are kind of niche uses so maybe it is less
important to optimize for those cases?
> 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)
