Contributing to Apache Kafka®: How to Write a KIP

Writing Kafka Improvement Proposals (KIPs) provides contributors with a structured way to propose even small public API or configuration changes while considering their effects on users, compatibility, testing, and migration. KIP-941 changed Kafka Streams’ RangeQuery implementation from Optional.of to Optional.ofNullable, allowing null bounds and eliminating repetitive application-side conditional logic without breaking existing code. KIP-1020 addressed misplaced Kafka Streams configuration by proposing deprecation of window.size.ms before moving responsibility to client configuration, with related discussion identifying another configuration that should follow a similar path. The KIP process begins with mailing-list discussion and requires three binding votes for acceptance, while its template encourages clear motivation, detailed proposed changes, compatibility planning, test strategy, and consideration of alternatives. The experience emphasizes that Apache Kafka’s community discussions are constructive and that careful deprecation practices, rather than abrupt removals, protect developers from disruptive upgrades and keep end-user needs central to software development.

No tracked trend matches for this post yet.

Use this post, company, and trend context to find content marketing opportunities, perform competitive analysis, or address product feature gaps via the Plushcap MCP server or the Plushcap API.