1. partition / member changes are caught on the server side, who will
notify consumers to re-balance.
2. topic changes are caught on the client side through metadata request,
who will then re-join the group with the new topic list to the server to
re-balance.
Guozhang
On Fri, Mar 6, 2015 at 8:49
Hi Guozhang,
Thanks for confirming.
It should be straightforward to make subscribe(TopicFilter) and
subscribe(TopicFilter, Partition) work for added/removed topics, since this
is mostly regex matching against zookeeper metadata. But any thoughts on
how repartitioning would work? (we need to let
Vinoth,
Yes we do have plans to continue supporting topic filters in 0.9 consumers,
the APIs are not there yet though.
Guozhang
On Thu, Mar 5, 2015 at 8:32 AM, Vinoth Chandar wrote:
> Hi guys,
>
> I was wondering what the plan in 0.9, was for the topic filters that are
> today in the High leve
