You are viewing a plain text version of this content. The canonical link for it is here.

Posted to jira@kafka.apache.org by "majialong (Jira)" <ji...@apache.org> on 2026/03/20 01:08:00 UTC

[jira] [Updated] (KAFKA-20340) SharePartition should keep only one config reference

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

majialong updated KAFKA-20340:
------------------------------
    Description: 
SharePartition currently holds both GroupConfigManager and ShareGroupConfigProvider. The fallback logic for group configs is split between them.

We should move all fallback logic into ShareGroupConfigProvider and remove the direct GroupConfigManager reference from SharePartition.

 

see https://github.com/apache/kafka/pull/21627#discussion_r2947410054

  was:
SharePartition currently holds both GroupConfigManager and ShareGroupConfigProvider. The fallback logic for group configs is split between them.

We should move all fallback logic into ShareGroupConfigProvider and remove the direct GroupConfigManager reference from SharePartition.


> SharePartition should keep only one config reference
> ----------------------------------------------------
>
>                 Key: KAFKA-20340
>                 URL: https://issues.apache.org/jira/browse/KAFKA-20340
>             Project: Kafka
>          Issue Type: Task
>            Reporter: majialong
>            Assignee: majialong
>            Priority: Minor
>
> SharePartition currently holds both GroupConfigManager and ShareGroupConfigProvider. The fallback logic for group configs is split between them.
> We should move all fallback logic into ShareGroupConfigProvider and remove the direct GroupConfigManager reference from SharePartition.
>  
> see https://github.com/apache/kafka/pull/21627#discussion_r2947410054



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