KIP-937 — Improve Message Timestamp Validation

Accepted Kafka 3.6 Broker

Adds a new log.message.timestamp.before.max.ms config (and optionally log.message.timestamp.after.max.ms) for brokers/topics to reject producer records whose CreateTime timestamp is too far in the past or future, returning INVALID_TIMESTAMP. The existing log.message.timestamp.difference.max.ms config was a symmetric bound that could not distinguish past vs. future violations, and its default of Long.MAX_VALUE allowed producers misconfigured with nanosecond timestamps to corrupt log retention behavior.

Details