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 DiscussionAccepted

Discussion thread: here

Voting Thread: herehere [Change the link from the KIP proposal email archive to your own email thread]

JIRA: here [Change the link from KAFKA-1 to your own ticket] 

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

With the recent deprecation of the #through method in Streams, there is no longer a need for the intermediateTopicsOption in the StreamsResetter tool. The plan is to currently log a warning when this option is used (since it is deprecated), and then in version 5.0 to officially remove it.

Public Interfaces

• StreamsResetter Tool
  • intermediateTopicsOption

Proposed Changes

We are planning to remove the intermediateTopicsOption from the StreamsResetter tool because with the removal of the #through method there is no longer a use-case/need for this option anymoreDescribe 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?
  • There will be no impact to current existing users
• If we are changing behavior how will we phase out the older behavior?
  • It will allow
• If we need special migration tools, describe them here.
  • No special migration tools are necessary for this change
• When will we remove the existing behavior?
  • In version 5.0

Test Plan

Describe in 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?

Rejected Alternatives

There is no need for addinal system tests

Rejected Alternatives

There were no other rejected alternativesIf 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.