[
https://issues.apache.org/jira/browse/KAFKA-15839?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Lianet Magrans updated KAFKA-15839:
-----------------------------------
Description:
TopicIdPartition is currently used in the reconciliation path. Could be used
more, just leaving topicPartitions when necessary for the callbacks and
interaction with the subscription state that does not fully support topic ids
yet
Ensure that we properly handle topic re-creation (same name, diff topic IDs) in
the reconciliation process (assignment cache, same assignment comparison, etc.)
was:
It is currently used in the reconciliation path. Could be used more, just
leaving topicPartitions when necessary for the callbacks and interaction with
the subscription state that does not fully support topic ids yet
Ensure that we properly handle topic re-creation (same name, diff topic IDs) in
the reconciliation process (assignment cache, same assignment comparison, etc.)
Summary: Review topic ID integration in consumer membershipManager
(was: Improve TopicIdPartition integration in consumer membershipManager)
> Review topic ID integration in consumer membershipManager
> ---------------------------------------------------------
>
> Key: KAFKA-15839
> URL: https://issues.apache.org/jira/browse/KAFKA-15839
> Project: Kafka
> Issue Type: Improvement
> Components: clients, consumer
> Reporter: Lianet Magrans
> Assignee: Lianet Magrans
> Priority: Major
> Labels: kip-848, kip-848-client-support, kip-848-e2e,
> kip-848-preview
> Fix For: 3.8.0
>
>
> TopicIdPartition is currently used in the reconciliation path. Could be used
> more, just leaving topicPartitions when necessary for the callbacks and
> interaction with the subscription state that does not fully support topic ids
> yet
> Ensure that we properly handle topic re-creation (same name, diff topic IDs)
> in the reconciliation process (assignment cache, same assignment comparison,
> etc.)
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
