You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@pulsar.apache.org by Apache Pulsar Slack <ap...@gmail.com> on 2020/07/15 09:11:03 UTC

Slack digest for #dev - 2020-07-15

2020-07-14 12:59:11 UTC - jimmy xie: @jimmy xie has joined the channel
----
2020-07-14 15:33:04 UTC - Raman Gupta: @Pedro Cardoso one more useful reference, here is how adding and removing consumers with Key_Shared mode in Pulsar: <https://github.com/apache/pulsar/wiki/PIP-34:-Add-new-subscribe-type-Key_shared> -- this is the (simpler) equivalent of incremental rebalance in Kafka
----
2020-07-15 02:23:47 UTC - zsh0139: @zsh0139 has joined the channel
----
2020-07-15 08:15:47 UTC - Pedro Cardoso: Thank you for the links Raman. Does pulsar provide a similar interface to Kafka’s rebalance listener to allow applications to know when a particular consumer has it’s key range that it listens to changed? 
The reason being that in Kafka, downstream code that can know when partitions have been assigned/removed to its consumer and apply stateful logic as part of that change. This is something I’ve been looking for in pulsar 
----