Hi Guozhang,
Thank you for your message!
The performance regression did not find its way to the 3.2 branch. In
other words, the commit that is fixed by your commit is not on branch 3.2.
Best,
Bruno
On 27.04.22 21:36, Guozhang Wang wrote:
Hi Bruno,
Could I also have this commit (
https://g
Hi Luke,
Thanks for your message!
I agree and I will include this PR in the next RC.
Best,
Bruno
On 28.04.22 09:38, Luke Chen wrote:
Hi Bruno,
I think this PR might also need to be included in next release candidate
because it's a bug fix/optimization for an issue introduced in v3.2.0.
https
Hi Bruno,
I think this PR might also need to be included in next release candidate
because it's a bug fix/optimization for an issue introduced in v3.2.0.
https://github.com/apache/kafka/pull/12096
cc Ismael
Thank you.
Luke
On Thu, Apr 28, 2022 at 3:36 AM Guozhang Wang wrote:
> Hi Bruno,
>
> C
Hi Bruno,
Could I also have this commit (
https://github.com/apache/kafka/commit/e026384ffb3170a2e71053a4163db58b9bd8fba6)
in the next release candidate? It's fixing a performance regression that
was just introduced, and not yet released in older versions.
Guozhang
On Tue, Apr 26, 2022 at 11:01
Hi, Bruno.
Thanks for the reply. Your understanding is correct. This is a regression
introduced only in the 3.2 branch.
Sorry for the late notice.
Jun
On Tue, Apr 26, 2022 at 10:04 AM Bruno Cadonna wrote:
> Hi Jun,
>
> Thank you for your message!
>
> Now I see how this issue was introduced in
Hi Jun,
Thank you for your message!
Now I see how this issue was introduced in 3.2.0. The fix for the bug
described in KAFKA-12841 introduced it, right? I initially understood
that the PR you want to include is the fix for the bug described in
KAFKA-12841 which dates back to 2.6.
I think th
