This page is meant as a template for writing a KIP. To create a KIP choose Tools->Copy on this page and modify with your content and replace the heading with the next KIP number and a description of your issue. Replace anything in italics with your own description.
Status
Current state: Under Discussion
Discussion thread: here [Change the link from the KIP proposal email archive to your own email thread]
JIRA:
Please keep the discussion on the mailing list rather than commenting on the wiki (wiki discussions get unwieldy fast).
Motivation
3.0 gives us the opportunity to make backwards incompatible changes. With that, now is a good time to change the default serde from `byte array` to `null`.
Public Interfaces
DEFAULT_KEY_SERDE_CLASS_CONFIG
will default to null
and DEFAULT_VALUE_SERDE_CLASS_CONFIG will default to null.
// Will return null if no default is set through configs public Serde defaultKeySerde() { } // Will return null if no default is set through configs public Serde defaultValueSerde() { }
Proposed Changes
Describe the new thing you want to do in appropriate detail. This may be fairly extensive and have large subsections of its own. Or it may be a few sentences. Use judgement based on the scope of the change.
Compatibility, Deprecation, and Migration Plan
- What impact (if any) will there be on existing users?
- If we are changing behavior how will we phase out the older behavior?
- If we need special migration tools, describe them here.
- When will we remove the existing behavior?
Rejected Alternatives
If there are alternative ways of accomplishing the same thing, what were they? The purpose of this section is to motivate why the design is the way it is and not some other way.