DUE TO SPAM, SIGN-UP IS DISABLED. Goto Selfserve wiki signup and request an account.
...
| Code Block | ||||
|---|---|---|---|---|
| ||||
{ "name": "TopologyDescription", "type": "TopologyDescription", "versions": "N+",
"nullableVersions": "N+", "default": "null",
"about": "The topology description for this group. Null if not available — see TopologyDescriptionStatus for the reason." },
{ "name": "TopologyDescriptionStatus", "type": "int8", "versions": "N+", "default": "0",
"about": "When TopologyDescription is null, the reason: 0=NOT_REQUESTED (client did not set IncludeTopologyDescription), 1=NOT_STORED (no topology description has been recorded for this group), 2=ERROR (the broker failed to fetch the topology description; check broker logs). Ignored when TopologyDescription is non-null." } |
The
...
TopologyDescription
...
common
...
struct
...
mirrors
...
the
...
struct
...
used
...
by
...
UpdateStreamsGroupTopologyDescriptionRequest
...
(same
...
field
...
names
...
and
...
shape).
...
Because
...
Kafka
...
RPC
...
schemas
...
do
...
not
...
share
...
common
...
structs
...
across
...
message
...
files,
...
the
...
struct
...
is
...
duplicated
...
in
...
StreamsGroupDescribeResponse.json.
Setting these fields does not change the ErrorCode on the DescribedGroup: a group with a successful describe but a missing or failed topology fetch still returns ErrorCode=NONE. The TopologyDescriptionStatus field tells the caller why TopologyDescription is null, so that "waiting for first push" (NOT_STORED) can be distinguished from "broker-side fetch failed" (ERROR) without an error-level change to the describe result.
...