> I think I’m actually OK with leaving it as leaveGroup with a lot of documentation that warns users away from changing it arbitrarily.
Pardon me, I just want to ensure we are all on the same page. 1. `leaveGroup=true`: `ClassicKafkaConsumer` sends a `LeaveGroupRequest` for either the dynamic or static member. 2. `leaveGroup=false`: `ClassicKafkaConsumer` does not send any ` LeaveGroupRequest` for either the dynamic or static member. 3. `leaveGroup=default` (current behavior): `ClassicKafkaConsumer` sends a `LeaveGroupRequest` for dynamic member, and it does NOT send any `ConsumerGroupHeartbeatRequest`for static member 4. `leaveGroup=true`: `AsyncKafkaConsumer` sends a `ConsumerGroupHeartbeatRequest` with "-1" epoch for either the dynamic or static member 5. `leaveGroup=false`: `AsyncKafkaConsumer` sends a `ConsumerGroupHeartbeatRequest` with "-2" epoch for the static member, and it does NOT send any `ConsumerGroupHeartbeatRequest` for dynamic member 6. `leaveGroup=default` (current behavior): `AsyncKafkaConsumer` sends a `ConsumerGroupHeartbeatRequest`with "-1" epoch for dynamic member and "-2" epoch for static member Best, Chia-Ping
