[jira] [Updated] (KAFKA-15283) Client support for OffsetFetch and OffsetCommit with topic ID

["Mickael Maison (Jira)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/KAFKA-15283?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Mickael Maison updated KAFKA-15283:
-----------------------------------
    Fix Version/s: 4.2.0
                       (was: 4.1.0)

> Client support for OffsetFetch and OffsetCommit with topic ID
> -------------------------------------------------------------
>
>                 Key: KAFKA-15283
>                 URL: https://issues.apache.org/jira/browse/KAFKA-15283
>             Project: Kafka
>          Issue Type: Sub-task
>          Components: clients, consumer
>            Reporter: Kirk True
>            Assignee: Lan Ding
>            Priority: Critical
>              Labels: kip-848-client-support, newbie, offset
>             Fix For: 4.2.0
>
>
> Currently, {{KafkaConsumer}} keeps track of topic IDs in the in-memory {{ConsumerMetadata}} object, and they are provided to the {{FETCH}} and {{METADATA}} RPC calls.
> With KIP-848 the OffsetFetch and OffsetCommit will start using topic IDs in the same way, so the new client implementation will provide it when issuing those requests. Topic names should continue to be supported as needed by the {{{}AdminClient{}}}.
> We should also review/clean-up the support for topic names in requests such as the {{METADATA}} request (currently supporting topic names as well as topic IDs on the client side).
> Tasks include:
>  * Introduce Topic ID in existing OffsetFetch and OffsetCommit API that will be upgraded on the server to support topic ID
>  * Check topic ID propagation internally in the client based on RPCs including it.
>  * Review existing support for topic name for potential clean if not needed.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)