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

Posted to jira@kafka.apache.org by "Jhen-Yung Hsu (Jira)" <ji...@apache.org> on 2025/07/16 10:37:00 UTC

[jira] [Updated] (KAFKA-19514) Deprecate and remove Properties from public API

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

Jhen-Yung Hsu updated KAFKA-19514:
----------------------------------
    Description: 
Currently, Kafka clients (Producer, Consumer, AdminClient) widely expose and accept configuration via java.util.Properties in their public API.

Properties has a few drawbacks, like the ones pointed out in https://issues.apache.org/jira/browse/KAFKA-19213, which and it has unnecessary concurrency overhead. On the other hand, Map is a more modern and flexible option.

  was:
Currently, Kafka clients (Producer, Consumer, AdminClient) widely expose and accept configuration via java.util.Properties in their public API.

Properties has a few drawbacks, like the ones pointed out in https://issues.apache.org/jira/browse/KAFKA-19213, and it has unnecessary concurrency overhead. On the other hand, Map is a more modern and flexible option.


> Deprecate and remove Properties from public API
> -----------------------------------------------
>
>                 Key: KAFKA-19514
>                 URL: https://issues.apache.org/jira/browse/KAFKA-19514
>             Project: Kafka
>          Issue Type: Bug
>            Reporter: Jhen-Yung Hsu
>            Assignee: Jhen-Yung Hsu
>            Priority: Minor
>
> Currently, Kafka clients (Producer, Consumer, AdminClient) widely expose and accept configuration via java.util.Properties in their public API.
> Properties has a few drawbacks, like the ones pointed out in https://issues.apache.org/jira/browse/KAFKA-19213, which and it has unnecessary concurrency overhead. On the other hand, Map is a more modern and flexible option.



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