log.retention.bytes is a broker-level config that sets the maximum size of a
topic partition on a broker, so it will apply to all topics…
unless a topic has the retention.bytes property configured — this is a
topic-level config and only applies to a single topic — in which case that
takes prece
I am running a Kafka cluster on Kubernetes. I am implementing a custom
PartitionAssignor to personalize the way topic partitions are assigned to
existing consumers in the consumer group. To this end, I am overriding the
method Map assign( Cluster metadata, Map subscriptions)
If inside the assi
Hi all
I have question about Kafka topic log retention on bytes, does the
log.retention.bytes apply to each topic or it apply to all topics in broker? If
it apply to each topic, then, when topic numbers keep growing in broker, how
can we make sure total disk size for all topic logs will not exc
I guess it's possible but very unlikely because it works perfectly with all
the previous versions and the current one? (2.5.1)
Why did a change in the version introduce NULLS there?
On Tue, Feb 23, 2021 at 9:16 PM Guozhang Wang wrote:
> Is it possible that the flattened values contain `null` and
