The other problem would be that kafka has no idea of the serdes you use in
your messages ie it only sees the key and value as bytes so it would be
difficult to implement generic filtering in the broker.
for your second problem it seems that creating separate topics for
respective destinations solv
Hi,
thx for reply.we have 2 situation to use server-side filter,that also
mean advantage consumer filter doen't have:
1.as Guozhang said,server filter would reduce network cost. we use aws
ec2 to provide kafka, all of them and kafka clients in different aws
regions to guarantee availability. ne
The reduction on network cost is a valid point: letting the consumer to do
the filtering would waste the network bandwidth as many bytes would be
dropped on the floor directly afterwards. But note that letting brokers to
filter on fetch response means that we cannot use nio zero-copy as we need
to
I do not think this will be implemented in the server. Why not simply create a
consumer that filters as required and outputs to a new topic?
> On Aug 28, 2019, at 7:48 AM, Xiangyuan LI wrote:
>
> Hi,
> I want to know whether kafka has any plan to filter message on
> server-side.this can reduce
Hi,
I want to know whether kafka has any plan to filter message on
server-side.this can reduce network flow obviously when many groups
subscribe the same one topic and only need part of message.
