Hey George,
there is no support for server side filtering based on key at the moment,
as it may significantly impact broker side performance.
On Thu, Jan 2, 2020 at 12:26 PM George wrote:
> Hi all
>
> is it possible to subscribe to a topic based on a specified key... without
> specifying the ho
Hi All,
We have a kafka cluster with 12 nodes and we are pretty much seeing 90% cpu
usage on all the nodes. Here is all the information. Need some help on
figuring out what the problem is and how to overcome this issue.
*Cluster:*
Kafka version: 2.3.0
Number of brokers in cluster: 12
Node type: 4
Hi Jan, unfortunately there is no easy or automatic way to do this.
Publishing null values directly to the changelog topics will remove them
from the topic, but it won't remove the corresponding row from the RocksDB
state store. (though deleting data programmatically from a state-store
WILL also r
Hey Jan,
although I believe your case is much more complicated, but would time based
retention work for you at all? If yes, time window store is like the best
option.
If no, streams has no out-of-box solution for invalidating the aggregation
record. It seems at least we could provide an API to in
Hi,
I have a rather complicated kafka streams application involving multiple
joins, aggregates, maps etc. At a certain point, parts of the data needs to
be removed throughout the entire streams topology, both in the topics, the
changelogs and the rocksdb state stores.
Managing this requires a lot
Hi all
is it possible to subscribe to a topic based on a specified key... without
specifying the hosting partition.
I know I can simply subscribe to the topic and filter the data as received
looking for relevant key, but I'd prefer to have this filter done on the
broker, reducing the consumer wor
Hello,
Greetings of the New Year to everybody. Sorry for reviving this randomly,
as I didn't have the original thread anymore.
I was reading through this KIP and trying to following the current vs
proposed diagrams. Once again, apologies for making mistakes in
understanding this.
Are we replacin