...

These components are less defined, and currently don’t have KIPs attached. Contributions are welcome to either suggest other extensions, or design one of the above extensions. Design, discussion, and voting on these is expected to begin after the integral KIPs are complete.

Public Interfaces

Briefly list any new interfaces that will be introduced as part of this proposal or any existing interfaces that will be removed or changed. The purpose of this section is to concisely call out the public contract that will come along with this feature.

A public interface is any change to the following:

• Binary log format

• The network protocol and api behavior

• Any class in the public packages under clientsConfiguration, especially client configuration

• org/apache/kafka/common/serialization

• org/apache/kafka/common

• org/apache/kafka/common/errors

• org/apache/kafka/clients/producer

• org/apache/kafka/clients/consumer (eventually, once stable)

• Monitoring

• Command line tools and arguments

• Anything else that will likely break existing users in some way when they upgrade

This KIP does not propose any new public interfaces; but its sub-KIPs will.

Compatibility, Deprecation, and Migration Plan

• What impact (if any) will there be on existing users?

...

• If we need special migration tools, describe them here.

• When will we remove the existing behavior?

This will be a backwards-compatible upgrade for existing Kafka Clusters. Diskless Topics will also support all existing APIs with the same external semantics as non-Diskless topics, including:

...

Specific compatibility, deprecation, and migration details will be covered in follow-up KIPs.

Test Plan

Describe in a few sentences how the KIP will be tested. We are mostly interested in system tests (since unit-tests are specific to implementation details). How will we know that the implementation works as expected? How will we know nothing broke?

There will be no modifications to existing tests for this KIP. Follow-up KIPs will have specific test plans.

Documentation Plan

...

There will be no modifications to the documentation for this KIP. Follow-up KIPs will have specific plans for changes to documentation.

Rejected Alternatives

...

Drop support for non-Diskless topics

...