delete+compact
retention policy, which can remove the record of an old key even if it is the latest value for that key and applies the segment-based data cleanup policy (1 day by default). However, StreamNative cannot remove compacted keys by retention time or size unless a tombstone (null value) message is written into the topic.max.compaction.lag.ms
and min.compaction.lag.ms
are not supported.delete.retention.ms
. In contrast, StreamNative/Pulsar removes the tombstone immediately.compaction-threshold
policy to control how often compression is triggered (default 100MB) it specifies how large the topic backlog can grow before compaction is triggered, or you can manually trigger compaction using the Pulsar administrative API. For more information, see Topic Compaction Cookbook.