fix: update CreateTopics API stage descriptions to use version 6

ryan-gang · ryan-gang · commit 966dc8d8e8c3 · 2025-07-17T12:15:53.000+05:30
Update all stage descriptions for the CreateTopics API to reference version 6 instead of version 7. This includes adjustments to the interactive protocol inspector links and the testing procedures to ensure consistency across all stages. The changes clarify the expected request and response structures for the API.
diff --git a/stage_descriptions/create-topics-01_yb1.md b/stage_descriptions/create-topics-01_yb1.md
@@ -6,8 +6,8 @@ The [CreateTopics API](https://kafka.apache.org/protocol#The_Messages_CreateTopi
 
 We've created an interactive protocol inspector for the request & response structures for `CreateTopics`:
 
-- 🔎 [CreateTopics Request (v7)](https://binspec.org/kafka-createtopics-request-v7)
-- 🔎 [CreateTopics Response (v7)](https://binspec.org/kafka-createtopics-response-v7)
+- 🔎 [CreateTopics Request (v6)](https://binspec.org/kafka-createtopics-request-v6)
+- 🔎 [CreateTopics Response (v6)](https://binspec.org/kafka-createtopics-response-v6)
 
 In this stage, you'll only need to add an entry for the `CreateTopics` API to the APIVersions response you implemented in earlier stages. This will let the client know that the broker supports the `CreateTopics` API. We'll get to responding to `CreateTopics` requests in later stages.
 
diff --git a/stage_descriptions/create-topics-02_ve7.md b/stage_descriptions/create-topics-02_ve7.md
@@ -14,8 +14,8 @@ If the topic name is invalid, the broker returns an error code of `17` (INVALID_
 
 We've created an interactive protocol inspector for the request & response structures for `CreateTopics`:
 
-- 🔎 [CreateTopics Request (v7)](https://binspec.org/kafka-createtopics-request-v7)
-- 🔎 [CreateTopics Response (v7)](https://binspec.org/kafka-createtopics-response-v7)
+- 🔎 [CreateTopics Request (v6)](https://binspec.org/kafka-createtopics-request-v6)
+- 🔎 [CreateTopics Response (v6)](https://binspec.org/kafka-createtopics-response-v6)
 
 In this stage, you'll need to implement basic topic name validation without needing to check against existing topics or system topics. You can hard code the error response for invalid topic names in this stage. 
 
@@ -27,7 +27,7 @@ The tester will execute your program like this:
 ./your_program.sh
 ```
 
-It'll then connect to your server on port 9092 and send a `CreateTopics` (v7) request with an invalid topic name.
+It'll then connect to your server on port 9092 and send a `CreateTopics` (v6) request with an invalid topic name.
 
 The tester will validate that:
 
diff --git a/stage_descriptions/create-topics-03_cb8.md b/stage_descriptions/create-topics-03_cb8.md
@@ -14,8 +14,8 @@ If the topic name is reserved, the broker returns an error code of `42` (INVALID
 
 We've created an interactive protocol inspector for the request & response structures for `CreateTopics`:
 
-- 🔎 [CreateTopics Request (v7)](https://binspec.org/kafka-createtopics-request-v7)
-- 🔎 [CreateTopics Response (v7)](https://binspec.org/kafka-createtopics-response-v7)
+- 🔎 [CreateTopics Request (v6)](https://binspec.org/kafka-createtopics-request-v6)
+- 🔎 [CreateTopics Response (v6)](https://binspec.org/kafka-createtopics-response-v6)
 
 We've also created an interactive protocol inspector for the `__cluster_metadata` topic's log file:
 - 🔎 [__cluster_metadata topic's log file](https://binspec.org/kafka-cluster-metadata)
@@ -30,7 +30,7 @@ The tester will execute your program like this:
 ./your_program.sh
 ```
 
-It'll then connect to your server on port 9092 and send a `CreateTopics` (v7) request with a reserved topic name.
+It'll then connect to your server on port 9092 and send a `CreateTopics` (v6) request with a reserved topic name.
 
 The tester will validate that:
 
diff --git a/stage_descriptions/create-topics-04_us2.md b/stage_descriptions/create-topics-04_us2.md
@@ -10,8 +10,8 @@ If the topic already exists, the broker returns an error code of `36` (TOPIC_ALR
 
 We've created an interactive protocol inspector for the request & response structures for `CreateTopics`:
 
-- 🔎 [CreateTopics Request (v7)](https://binspec.org/kafka-createtopics-request-v7)
-- 🔎 [CreateTopics Response (v7)](https://binspec.org/kafka-createtopics-response-v7)
+- 🔎 [CreateTopics Request (v6)](https://binspec.org/kafka-createtopics-request-v6)
+- 🔎 [CreateTopics Response (v6)](https://binspec.org/kafka-createtopics-response-v6)
 
 We've also created an interactive protocol inspector for the `__cluster_metadata` topic's log file:
 - 🔎 [__cluster_metadata topic's log file](https://binspec.org/kafka-cluster-metadata)
@@ -30,7 +30,7 @@ The tester will execute your program like this:
 # Then try to create the same topic again
 ```
 
-It'll then connect to your server on port 9092 and send a `CreateTopics` (v7) request for an existing topic.
+It'll then connect to your server on port 9092 and send a `CreateTopics` (v6) request for an existing topic.
 
 The tester will validate that:
 
diff --git a/stage_descriptions/create-topics-05_hh9.md b/stage_descriptions/create-topics-05_hh9.md
@@ -17,8 +17,8 @@ The response should be identical to what would be returned for actual topic crea
 
 We've created an interactive protocol inspector for the request & response structures for `CreateTopics`:
 
-- 🔎 [CreateTopics Request (v7)](https://binspec.org/kafka-createtopics-request-v7)
-- 🔎 [CreateTopics Response (v7)](https://binspec.org/kafka-createtopics-response-v7)
+- 🔎 [CreateTopics Request (v6)](https://binspec.org/kafka-createtopics-request-v6)
+- 🔎 [CreateTopics Response (v6)](https://binspec.org/kafka-createtopics-response-v6)
 
 In this stage, you'll need to check the `validate_only` flag in the request and modify your behavior accordingly.
 
@@ -30,7 +30,7 @@ The tester will execute your program like this:
 ./your_program.sh
 ```
 
-It'll then connect to your server on port 9092 and send a `CreateTopics` (v7) request with `validate_only` set to `true`.
+It'll then connect to your server on port 9092 and send a `CreateTopics` (v6) request with `validate_only` set to `true`.
 
 The tester will validate that:
 
diff --git a/stage_descriptions/create-topics-06_fl3.md b/stage_descriptions/create-topics-06_fl3.md
@@ -17,8 +17,8 @@ Mixed success/failure scenarios are handled gracefully - if one topic fails vali
 
 We've created an interactive protocol inspector for the request & response structures for `CreateTopics`:
 
-- 🔎 [CreateTopics Request (v7)](https://binspec.org/kafka-createtopics-request-v7)
-- 🔎 [CreateTopics Response (v7)](https://binspec.org/kafka-createtopics-response-v7)
+- 🔎 [CreateTopics Request (v6)](https://binspec.org/kafka-createtopics-request-v6)
+- 🔎 [CreateTopics Response (v6)](https://binspec.org/kafka-createtopics-response-v6)
 
 ## Tests
 
@@ -28,7 +28,7 @@ The tester will execute your program like this:
 ./your_program.sh
 ```
 
-It'll then connect to your server on port 9092 and send a `CreateTopics` (v7) request with multiple topics.
+It'll then connect to your server on port 9092 and send a `CreateTopics` (v6) request with multiple topics.
 
 The tester will validate that:
 
diff --git a/stage_descriptions/create-topics-07_rk2.md b/stage_descriptions/create-topics-07_rk2.md
@@ -18,8 +18,8 @@ TODO
 
 We've created an interactive protocol inspector for the request & response structures for `CreateTopics`:
 
-- 🔎 [CreateTopics Request (v7)](https://binspec.org/kafka-createtopics-request-v7)
-- 🔎 [CreateTopics Response (v7)](https://binspec.org/kafka-createtopics-response-v7)
+- 🔎 [CreateTopics Request (v6)](https://binspec.org/kafka-createtopics-request-v6)
+- 🔎 [CreateTopics Response (v6)](https://binspec.org/kafka-createtopics-response-v6)
 
 We've also created an interactive protocol inspector for the `__cluster_metadata` topic's log file:
 - 🔎 [__cluster_metadata topic's log file](https://binspec.org/kafka-cluster-metadata)
@@ -32,7 +32,7 @@ The tester will execute your program like this:
 ./your_program.sh
 ```
 
-It'll then connect to your server on port 9092 and send a `CreateTopics` (v7) request with valid parameters.
+It'll then connect to your server on port 9092 and send a `CreateTopics` (v6) request with valid parameters.
 
 The tester will validate that:
 
diff --git a/stage_descriptions/createtopics.md b/stage_descriptions/createtopics.md
@@ -52,7 +52,7 @@ The tester will execute your program like this:
 ./your_program.sh
 ```
 
-It'll then connect to your server on port 9092 and send a `CreateTopics` (v7) request with an invalid topic name.
+It'll then connect to your server on port 9092 and send a `CreateTopics` (v6) request with an invalid topic name.
 
 The tester will validate that:
 
@@ -88,7 +88,7 @@ The tester will execute your program like this:
 ./your_program.sh
 ```
 
-It'll then connect to your server on port 9092 and send `CreateTopics` (v7) requests with invalid parameters.
+It'll then connect to your server on port 9092 and send `CreateTopics` (v6) requests with invalid parameters.
 
 The tester will validate that:
 
@@ -125,7 +125,7 @@ The tester will execute your program like this:
 # Then try to create the same topic again
 ```
 
-It'll then connect to your server on port 9092 and send a `CreateTopics` (v7) request for an existing topic.
+It'll then connect to your server on port 9092 and send a `CreateTopics` (v6) request for an existing topic.
 
 The tester will validate that:
 
@@ -162,7 +162,7 @@ The tester will execute your program like this:
 ./your_program.sh
 ```
 
-It'll then connect to your server on port 9092 and send `CreateTopics` (v7) requests with invalid manual assignments.
+It'll then connect to your server on port 9092 and send `CreateTopics` (v6) requests with invalid manual assignments.
 
 The tester will validate that:
 
@@ -197,7 +197,7 @@ The tester will execute your program like this:
 ./your_program.sh
 ```
 
-It'll then connect to your server on port 9092 and send `CreateTopics` (v7) requests without proper authorization.
+It'll then connect to your server on port 9092 and send `CreateTopics` (v6) requests without proper authorization.
 
 The tester will validate that:
 
