s
> add-on feature, or its impact.
>
> Boyang
>
>
> From: Georg Friedrich
> Sent: Tuesday, October 8, 2019 6:26 AM
> To: dev@kafka.apache.org
> Subject: RE: group.instance.id for StickyAssignors
>
> Hi Matthias,
>
> Let's
t; add-on feature, or its impact.
>
> Boyang
>
>
> From: Georg Friedrich
> Sent: Tuesday, October 8, 2019 6:26 AM
> To: dev@kafka.apache.org
> Subject: RE: group.instance.id for StickyAssignors
>
> Hi Matthias,
>
> Let's see if I
if I got something wrong.
Thanks in advance for your help.
Kind regards
Georg Friedrich
-Original Message-
From: Matthias J. Sax
Sent: Monday, October 7, 2019 2:34 PM
To: dev@kafka.apache.org
Subject: Re: group.instance.id for StickyAssignors
`groud.instance.id` is for static group membe
ng.
Thanks in advance for your help.
Kind regards
Georg Friedrich
-Original Message-
From: Matthias J. Sax
Sent: Monday, October 7, 2019 2:34 PM
To: dev@kafka.apache.org
Subject: Re: group.instance.id for StickyAssignors
`groud.instance.id` is for static group membership.
What advant
`groud.instance.id` is for static group membership.
What advantage to you imply by re-using it for (Cooperative)StickyAssignor?
>> As far as I understand this would make the behavior of those assignors more
>> predictable.
Can you elaborate?
I am not aware of any re-use, and I personally belie
Hi,
I'm wondering whether it is planned to make use of the group.instance.id also
in the (Cooperative)StickyAssignor.
As far as I understand this would make the behavior of those assignors more
predictable.
Maybe you have some information on this or whether I should open a Jira-Ticket
for it.
T
