dajac merged PR #15053:
URL: https://github.com/apache/kafka/pull/15053
--
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: jira-unsubscr...@kafka.apache.or
dajac commented on PR #15053:
URL: https://github.com/apache/kafka/pull/15053#issuecomment-1866183110
It is impossible to get a clean build at the moment. There are OOM errors
all over the places, including in trunk. Looking at all the builds, it is clear
that this PR does not create persis
dajac commented on PR #15053:
URL: https://github.com/apache/kafka/pull/15053#issuecomment-1864868557
@jeffkbkim The goal is to have something better than
`group.coordinator.new.enable`. Yes, I will add it to the KIP.
--
This is an automated message from the Apache Git Service.
To respond
jeffkbkim commented on PR #15053:
URL: https://github.com/apache/kafka/pull/15053#issuecomment-1864862018
is the purpose of this config to prevent EA users from accidentally using
the consumer protocol while using the new coordinator?
also, should we update the kip with this new confi
dajac opened a new pull request, #15053:
URL: https://github.com/apache/kafka/pull/15053
This patch adds the `group.coordinator.rebalance.protocols` configuration
which accepts a list of protocols to enable. At the moment, only `generic` and
`consumer` are supported and it is not possible t
