• Status
• Motivation
• Proposed Change
• New and Changed Public Interfaces
• Migration Plan and Compatibility
• Rejected Alternatives

Status

Current state: Under Discussion

Discussion thread: https://lists.apache.org/thread/01bs42crlkn5jr1r846vflp293zv2t86

JIRA: KAFKA-1974920018

Motivation

The `kafka-feature.sh` command-line tool currently has two issues that impact usability and consistency:

...

Since this is a breaking change, it should be introduced in 5.0. A warning message will be added to the argument group helping string in 4.x telling users that the group will be removed from the top level and become arguments under specific commands.

...

A new boolean flag, `--unstable-feature-versions`, will be added to the `version-mapping` subcommand in both `kafka-feature.sh` and `kafka-storage.sh`. When this flag is present, the tool will call `MetadataVersion.fromVersionString()` with the unstableFeatureVersionsEnabled flag set to true, allowing users to see feature mappings for development and testing versions. By default (without the flag), only production/stable metadata versions will be included.

Excluding unstable feature versions is the behavior before KAFKA-19544, so this is not a breaking change and can be introduced in 4.x.

New and Changed Public Interfaces

...