@xiowu0 Thanks much for the PR. The fix makes sense overall. Since bug kind of exists even before the fix made in KAFKA-7322, it probably makes sense to have a separate JIRA to document the problem and the solution. I opened https://issues.apache.org/jira/browse/KAFKA-7441 and also updated the PR title accordingly. Please feel free to modify the JIRA, PR title and description as appropriate.
I have one high level comment regarding the test. If the problem description in KAFKA-7441 makes sense, then the bug can be triggered without having user changing the policy, right? Can we make the test more general, ideally just simulating the scenario described in the JIRA, without requiring topic policy switch to trigger the bug? [ Full content available at: https://github.com/apache/kafka/pull/5694 ] This message was relayed via gitbox.apache.org for [email protected]
