Table of Contents |
---|
Status
Current state: Accepted
Under Discussion thread: here
Discussion Vote thread: here
JIRA: Jira server ASF JIRA columns key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution serverId 5aa69414-a9e9-3523-82ec-879b028fb15b key KAFKA-6774
...
This has been summarized in table below.
When using subscribe(...) (group management) | When using assign(...) (standalone consumer) | |
---|---|---|
group.id ="" | InvalidGroupException |
|
This can be confusing to users as they would likely expect the consumer treat the default group id the same way in these two cases. Using the default group id of ""
is troublesome, and consumers are not normally expected to do that in a production setting. This KIP proposes deprecating the empty group id on the client, and changing the default group id to null
so that unnecessary and unintentional offset fetches and commits are avoided.
...
This is how these two group ids will work
When using subscribe(...) (group management) | When using | |
---|---|---|
| InvalidGroupException |
|
OffsetCommit
protocol below) and
|
|
|
InvalidGroupException |
|
Client Side Deprecation
The use of empty group id will be deprecated on the client. A warning log will appear on clients that use this group id.
...