[
https://issues.apache.org/jira/browse/KAFKA-12975?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17370944#comment-17370944
]
Jason Gustafson commented on KAFKA-12975:
-----------------------------------------
I think the main guarantee we want is that offsets cannot be mistakenly reused
on a recreated topic. Once a topic is gone, all its offsets (persistent or
otherwise) need to go with it. Ideally the consumer would get a notification in
the rebalance listener that the topic was recreated so that the user has a
chance to set the initial position. As a starting place, we can associate the
in-memory fetch position in the consumer with the topicId that is being
fetched. Then if we find the topic ID is deleted, we should delete the position
in memory and consult the reset policy.
> Consider how Topic IDs can improve consume experience
> -----------------------------------------------------
>
> Key: KAFKA-12975
> URL: https://issues.apache.org/jira/browse/KAFKA-12975
> Project: Kafka
> Issue Type: Sub-task
> Reporter: Justine Olshan
> Priority: Major
>
> Currently when a consumer subscribes to a topic, it will continue to consume
> from this topic across topic deletions and recreations with the same name. By
> adding topic IDs to the consumer, we will have more insight for these events.
> We should figure out if we want to change consumer logic now that we have
> this information.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
