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

Posted to jira@kafka.apache.org by "Mickael Maison (Jira)" <ji...@apache.org> on 2026/10/08 07:33:00 UTC

[jira] [Commented] (KAFKA-21242) Migrate Scala LogManager#apply to Java LogManger#create

    [ https://issues.apache.org/jira/browse/KAFKA-21242?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18124872#comment-18124872 ] 

Mickael Maison commented on KAFKA-21242:
----------------------------------------

We already had https://issues.apache.org/jira/browse/KAFKA-20390 for this work

> Migrate Scala LogManager#apply to Java LogManger#create
> -------------------------------------------------------
>
>                 Key: KAFKA-21242
>                 URL: https://issues.apache.org/jira/browse/KAFKA-21242
>             Project: Kafka
>          Issue Type: Improvement
>            Reporter: Chia-Ping Tsai
>            Assignee: Chia-Ping Tsai
>            Priority: Minor
>
> {{kafka.log.LogManager#apply}} is a thin Scala factory that extracts config values from {{KafkaConfig}} and passes them to the Java {{LogManager}} constructor. We can move it to storage as {{LogManager#create(AbstractConfig, ...)}} and remove the Scala object.
> Probably we can introduce a {{LogManagerConfig}} to consolidate those separate config items, which also shortens the constructor



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