Skip to content

MINOR: Bump LATEST_PRODUCTION to 4.2-IV1 in 4.2 branch #20972

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
AndrewJSchofield wants to merge 2 commits into from
Closed

MINOR: Bump LATEST_PRODUCTION to 4.2-IV1 in 4.2 branch #20972

Show file tree
Hide file tree
Changes from 1 commit
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
267ca9e
MINOR: Bump LATEST_PRODUCTION to 4.2-IV1
AndrewJSchofield Nov 24, 2025
5383c17
Test fixes
AndrewJSchofield Nov 24, 2025
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
8 changes: 8 additions & 0 deletions metadata/src/test/java/org/apache/kafka/metadata/storage/FormatterTest.java
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -34,6 +34,8 @@
import org.apache.kafka.server.common.GroupVersion;
import org.apache.kafka.server.common.KRaftVersion;
import org.apache.kafka.server.common.MetadataVersion;
import org.apache.kafka.server.common.ShareVersion;
import org.apache.kafka.server.common.StreamsVersion;
import org.apache.kafka.server.common.TestFeatureVersion;
import org.apache.kafka.server.common.TransactionVersion;
import org.apache.kafka.test.TestUtils;
Expand Down Expand Up @@ -391,6 +393,12 @@ public void testFeatureFlag(short version) throws Exception {
expected.add(new ApiMessageAndVersion(new FeatureLevelRecord().
setName(GroupVersion.FEATURE_NAME).
setFeatureLevel(GroupVersion.GV_1.featureLevel()), (short) 0));
expected.add(new ApiMessageAndVersion(new FeatureLevelRecord().
setName(ShareVersion.FEATURE_NAME).
setFeatureLevel(ShareVersion.SV_1.featureLevel()), (short) 0));
expected.add(new ApiMessageAndVersion(new FeatureLevelRecord().
setName(StreamsVersion.FEATURE_NAME).
setFeatureLevel(StreamsVersion.SV_1.featureLevel()), (short) 0));
if (version > 0) {
expected.add(new ApiMessageAndVersion(new FeatureLevelRecord().
setName(TestFeatureVersion.FEATURE_NAME).
Expand Down
15 changes: 9 additions & 6 deletions server-common/src/main/java/org/apache/kafka/server/common/MetadataVersion.java
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -114,18 +114,21 @@ public enum MetadataVersion {
// Send FETCH version 18 in the replica fetcher (KIP-1166)
IBP_4_1_IV1(27, "4.1", "IV1", false),

// Enables share groups by default for new clusters (KIP-932).
IBP_4_2_IV0(28, "4.2", "IV0", false),

// Enables "streams" groups by default for new clusters (KIP-1071).
IBP_4_2_IV1(29, "4.2", "IV1", false),

//
// NOTE: MetadataVersions after this point are unstable and may be changed.
// If users attempt to use an unstable MetadataVersion, they will get an error unless
// they have set the configuration unstable.feature.versions.enable=true.
// Please move this comment when updating the LATEST_PRODUCTION constant.
//

// Enables share groups by default for new clusters (KIP-932).
IBP_4_2_IV0(28, "4.2", "IV0", false),

// Enables "streams" groups by default for new clusters (KIP-1071).
IBP_4_2_IV1(29, "4.2", "IV1", false);
// Placeholder testing level for 4.3.
IBP_4_3_IV0(30, "4.3", "IV0", false);

// NOTES when adding a new version:
// Update the default version in @ClusterTest annotation to point to the latest version
Expand All @@ -145,7 +148,7 @@ public enum MetadataVersion {
* <strong>Think carefully before you update this value. ONCE A METADATA VERSION IS PRODUCTION,
* IT CANNOT BE CHANGED.</strong>
*/
public static final MetadataVersion LATEST_PRODUCTION = IBP_4_1_IV1;
public static final MetadataVersion LATEST_PRODUCTION = IBP_4_2_IV1;
// If you change the value above please also update
// LATEST_STABLE_METADATA_VERSION version in tests/kafkatest/version.py

Expand Down
11 changes: 5 additions & 6 deletions server-common/src/test/java/org/apache/kafka/server/common/MetadataVersionTest.java
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -90,16 +90,15 @@ public void testFromVersionString() {
assertEquals(IBP_4_1_IV0, MetadataVersion.fromVersionString("4.1-IV0", true));
assertEquals(IBP_4_1_IV1, MetadataVersion.fromVersionString("4.1-IV1", true));

// 4.2-IV1 is the latest production version in the 4.2 line
assertEquals(IBP_4_2_IV1, MetadataVersion.fromVersionString("4.2", true));
assertEquals(IBP_4_2_IV0, MetadataVersion.fromVersionString("4.2-IV0", true));
assertEquals(IBP_4_2_IV1, MetadataVersion.fromVersionString("4.2-IV1", true));

// Throws exception when unstableFeatureVersionsEnabled is false
assertEquals("Unknown metadata.version '4.2-IV0'. Supported metadata.version are: 3.3-IV3, 3.4-IV0, 3.5-IV0, 3.5-IV1, 3.5-IV2, "
+ "3.6-IV0, 3.6-IV1, 3.6-IV2, 3.7-IV0, 3.7-IV1, 3.7-IV2, 3.7-IV3, 3.7-IV4, 3.8-IV0, 3.9-IV0, 4.0-IV0, 4.0-IV1, 4.0-IV2, 4.0-IV3, 4.1-IV0, 4.1-IV1",
assertThrows(IllegalArgumentException.class, () -> fromVersionString("4.2-IV0", false)).getMessage());
assertEquals("Unknown metadata.version '4.2-IV1'. Supported metadata.version are: 3.3-IV3, 3.4-IV0, 3.5-IV0, 3.5-IV1, 3.5-IV2, "
+ "3.6-IV0, 3.6-IV1, 3.6-IV2, 3.7-IV0, 3.7-IV1, 3.7-IV2, 3.7-IV3, 3.7-IV4, 3.8-IV0, 3.9-IV0, 4.0-IV0, 4.0-IV1, 4.0-IV2, 4.0-IV3, 4.1-IV0, 4.1-IV1",
assertThrows(IllegalArgumentException.class, () -> fromVersionString("4.2-IV1", false)).getMessage());
assertEquals("Unknown metadata.version '4.3-IV0'. Supported metadata.version are: 3.3-IV3, 3.4-IV0, 3.5-IV0, 3.5-IV1, 3.5-IV2, "
+ "3.6-IV0, 3.6-IV1, 3.6-IV2, 3.7-IV0, 3.7-IV1, 3.7-IV2, 3.7-IV3, 3.7-IV4, 3.8-IV0, 3.9-IV0, 4.0-IV0, 4.0-IV1, 4.0-IV2, 4.0-IV3, 4.1-IV0, 4.1-IV1, 4.2-IV0, 4.2-IV1",
assertThrows(IllegalArgumentException.class, () -> fromVersionString("4.3-IV0", false)).getMessage());
}

@Test
Expand Down
5 changes: 3 additions & 2 deletions tests/kafkatest/version.py
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -132,7 +132,7 @@ def get_version(node=None):

LATEST_STABLE_TRANSACTION_VERSION = 2
# This should match the LATEST_PRODUCTION version defined in MetadataVersion.java
LATEST_STABLE_METADATA_VERSION = "4.1-IV1"
LATEST_STABLE_METADATA_VERSION = "4.2-IV1"

# 2.1.x versions
V_2_1_0 = KafkaVersion("2.1.0")
Expand Down Expand Up @@ -248,4 +248,5 @@ def get_version(node=None):

# 4.2.x version
V_4_2_0 = KafkaVersion("4.2.0")
LATEST_4_2 = V_4_2_0
V_4_2_1 = KafkaVersion("4.2.1")
LATEST_4_2 = V_4_2_1

@mjsax mjsax Nov 24, 2025

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I don't think we need this change yet? As a matter of fact, not even sure why the whole section for 4.2 already exists? We only add released versions here (and 4.2.0 is not release yet, and should only be added in trunk after 4.2.0 was release...) Sure, it doesn't hurt to add it, but it's dead code.

@chia7712 chia7712 Nov 24, 2025

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This code was added by #20471 to prevent the use of new configurations in order kafka tools, we could remove the entire 4.2 section by reversing the version check condition. self >= V_4_2_0 -> self <= LATEST_4_1

@mjsax mjsax Nov 25, 2025

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I see. Thanks for clarifying. Guess, for 4.2 branch we don't really use LATEST_4_2 anywhere else, so it might be fine. And the test code you refer to uses V_4_2_0 explicitly.

Bottom line: I understand why we needed to add V_4_2_0, but both LATEST_4_2 and V_4_2_1 seem not to be necessary for 4.2 branch, and especially pointing LATEST_4_2 to an unreleased version seems odd (even if it does not break anything as it's unused).

@AndrewJSchofield AndrewJSchofield Nov 25, 2025

Copy link
Copy Markdown
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I realise now that I was getting confused between Kafka versions and metadata versions.

Loading