[
https://issues.apache.org/jira/browse/KAFKA-5207?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Matt Farmer resolved KAFKA-5207.
--------------------------------
Resolution: Fixed
Heh, it was pointed out to me that assignment is an overwrite operation, not a
cumulative operation.
> Addition of a way to manually revoke individual partitions from a consumer
> --------------------------------------------------------------------------
>
> Key: KAFKA-5207
> URL: https://issues.apache.org/jira/browse/KAFKA-5207
> Project: Kafka
> Issue Type: Improvement
> Components: consumer
> Reporter: Matt Farmer
>
> The {{Consumer.assign}} call permits us to manually assign topic and
> partition pairs to a consumer. Unfortunately, there is no equivalent that
> allows us to manually _revoke_ those partitions from the consumer. I'd like
> to propose the addition of a {{Consumer.revoke}} that also takes a
> {{Collection<TopicPartition>}} that will cause the Consumer to stop seeing
> messages from that topic and partition pair in a manually assigned scenario.
> For some wider context on this request: I'm working on a problem where I need
> two Consumers to consume from different topics on different threads. But the
> topics are partitioned identically, and so if Consumer A is subscribed to
> partition 3, Consumer B also needs to be subscribed to partition 3.
> The addition of this API would permit me to let Consumer A's partition
> assignments be managed by Kafka, and allow me to use a
> {{ConsumerRebalanceListener}} to tweak Consumer B's configuration when
> there's a rebalance event.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
