This Confluence has been LDAP enabled, if you are an ASF Committer, please use your LDAP Credentials to login. Any problems file an INFRA jira ticket please.

Child pages
  • KIP-322: Return new error code for DeleteTopics API when topic deletion disabled.
Skip to end of metadata
Go to start of metadata

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 stateUnder Discussion

Discussion thread: here 

JIRA: KAFKA-5975 - Getting issue details... STATUS

Released: 2.1.0

Please keep the discussion on the mailing list rather than commenting on the wiki (wiki discussions get unwieldy fast).

Motivation

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

  1. Bump DeleteTopics protocol version to V3 (with same schema as V2)
  2. 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

  • Instead of timing out, V2 and older version delete topic requests will get INVALID_REQUEST
  • No labels