lianetm commented on PR #21464: URL: https://github.com/apache/kafka/pull/21464#issuecomment-3922314818
As for the follow-ups: - here is the PR with the integration tests to validate the different responses depending on topicId/name https://github.com/apache/kafka/pull/21509 - checked UNSTABLE_OFFSET case, it's ok because it just propagates the `UnstableOffsetCommitException` (which is retriable) - as the the UNKNOWN_TOPIC_OR_PARTITION, it's indeed never returned by the broker on the offsetfetch path anymore, but it was returned by older broker (e.g, [3.1](https://github.com/apache/kafka/blob/2b57b38f9306ac73f18d94d55c0158530fd444df/core/src/main/scala/kafka/server/KafkaApis.scala#L1344-L1345) broker when using zookeeper and not finding the topic for the offsets there). So I guess we should keep the handling on the client for backwards compatibility -- 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. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
