...
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
JIRA:
Jira | ||||||
---|---|---|---|---|---|---|
|
Released: 2.1.0here
Please keep the discussion on the mailing list rather than commenting on the wiki (wiki discussions get unwieldy fast).
Motivation
Describe the problems you are trying to solve.
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
Proposed Changes
...
Currently when we use deleteTopics API with topic deletion disabled on server, then the client cannot get a response and fails returning a timeout error.
This KIP is to return proper error code in above mentioned scenario.
Public Interfaces
If topic deletion feature is disabled , DeleteTopicsAPI response
will return TOPIC_DELETION_DISABLED error code.
public class TopicDeletionDisabledException extends ApiException {
private static final long serialVersionUID = 1L;
public TopicDeletionDisabledException() {
}
public TopicDeletionDisabledException(String message) {
super(message);
}
}
Proposed Changes
The proposal is to
- Bump DeleteTopics protocol version to V3 (with same schema as V2)
- If topic deletion is disabled on broker:
For V2 and previous versions, return INVALID_REQUEST
For V3 and above requests, return TopicDeletionDisabledException
Compatibility, Deprecation, and Migration Plan
- The change is backwards compatible.Instead of timing out, V2 and older version delete topic requests will get INVALID_REQUEST