jolshan commented on a change in pull request #9944:
URL: https://github.com/apache/kafka/pull/9944#discussion_r655649094
##########
File path:
clients/src/main/java/org/apache/kafka/common/requests/FetchResponse.java
##########
@@ -71,6 +79,14 @@ public FetchResponseData data() {
return data;
}
+ /**
+ * From version 3 or later, the authorized and existing entries in
`FetchRequest.fetchData` should be in the same order in `responseData`.
+ * Version 13 introduces topic IDs which can lead to a few new errors. If
there is any unknown topic ID in the request, the
+ * response will contain a top-level UNKNOWN_TOPIC_ID error and
UNKNOWN_TOPIC_ID errors on all the partitions.
+ * If a request's topic ID usage is inconsistent with the session, we will
return a top level FETCH_SESSION_TOPIC_ID_ERROR error.
+ * We may also return INCONSISTENT_TOPIC_ID error as a top-level error as
well as an error for a given partition when that partition in the session has a
topic ID
Review comment:
It is both a top level and partition error here. I kind of like being
able to identify the partition (kind of wish the other errors could do this in
some cases), but we can change this.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
