...

Current state: Under Discussion

Discussion thread: here 

JIRA:

Released: 2.1.0here 

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

...

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 If topic deletion is disabledreturn 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