chickenchickenlove commented on PR #20362: URL: https://github.com/apache/kafka/pull/20362#issuecomment-3437134660
@lianetm It looks like a commit masked the issue I was trying to fix. 1. I tested and debugged to solve this problem based on commit hash (986322dc36) 2. Currently, this PR based on commit hash (88616295e1) In this branch, I reverted this PR(https://github.com/apache/kafka/commit/38e3359446963f23d1d068abcaa1eb8a51fc30cc) to check `HandlingSourceTopicDeletionIntegrationTest` can be success with `new consumer protocol`. But, it never success. However, If I tested it based on 986322dc36, `HandlingSourceTopicDeletionIntegrationTest` is always success. In other words, one of the PRs between those two commits made the `HandlingSourceTopicDeletionIntegrationTest#shouldThrowErrorAfterSourceTopicDeleted` test permanently fail. That is, it succeeds under the legacy protocol but fails under the new protocol. To put it differently, in the legacy protocol, when a topic is deleted, all Stream Threads are expected to transition to the Error state, whereas in the new protocol, when a topic is deleted, all Stream Threads remain in the Running state. Is this the expected behavior for the new protocol in Kafka Streams? -- 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]
