showuon commented on pull request #10750: URL: https://github.com/apache/kafka/pull/10750#issuecomment-847654763
@DuongPTIT , thanks for the PR. One important question to you before reviewing the code: could you confirm this issue only happen in V2.5, and not V2.8? I'm not sure if we will have another minor release for V2.5 ( I don't think it's highly possible because it's 4 releases ago). That means, even your fix merge into V2.5, you might not be able to upgrade Kafka to get this fix. Usually we merge to trunk first, and then back port to older release. So, if you can confirm this issue will happen in V2.8 or `trunk` branch, it will get fixed in next release definitely! Thank you. -- 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
