KIP-468 — Avoid decompression of record when validate record at server in the scene of inPlaceAssignment .

Discussion ProtocolBroker

KIP-468 proposes adding batch-level metadata fields (`batch.min.timestamp`, `records.number`, `all.key.is.null`) to the record batch header so the broker can validate timestamp, offset count, and null-key constraints for log-compacted topics without decompressing the entire batch. Profiling showed that full batch decompression for validation was consuming 60–97% of broker CPU in high-throughput scenarios, acting as a throughput bottleneck at ~600 MB/s network ingress.

Details