[
https://issues.apache.org/jira/browse/KAFKA-19570?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Lucas Brutschy updated KAFKA-19570:
-----------------------------------
Description:
Offline migration essentially preserves offsets and nothing else. So
effectively write tombstones for classic group type when a streams heartbeat is
sent to with the group ID of an empty classic group, and write tombstones for
the streams group type when a classic consumer attempts to join with a group ID
of an empty streams group.
AC:
* Implementation on the broker-side
was:
Offline migration would essentially preserve offsets and nothing else. So
effectively write tombstones for classic group type when a streams heartbeat is
sent to with the group ID of an empty classic group, and write tombstones for
the streams group type when a classic consumer attempts to join with a group ID
of an empty streams group.
You can check getOrMaybeCreateConsumerGroup for an example.
AC:
* Implementation on the broker-side
> Implement offline migration
> ---------------------------
>
> Key: KAFKA-19570
> URL: https://issues.apache.org/jira/browse/KAFKA-19570
> Project: Kafka
> Issue Type: Sub-task
> Reporter: Lucas Brutschy
> Assignee: Lucas Brutschy
> Priority: Major
> Labels: streams
>
> Offline migration essentially preserves offsets and nothing else. So
> effectively write tombstones for classic group type when a streams heartbeat
> is sent to with the group ID of an empty classic group, and write tombstones
> for the streams group type when a classic consumer attempts to join with a
> group ID of an empty streams group.
> AC:
> * Implementation on the broker-side
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
