You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@kafka.apache.org by "Sagar Rao (Jira)" <ji...@apache.org> on 2024/04/23 11:08:00 UTC

[jira] [Created] (KAFKA-16604) Deprecate ConfigDef.ConfigKey constructor from public APIs

Sagar Rao created KAFKA-16604:
---------------------------------

             Summary: Deprecate ConfigDef.ConfigKey constructor from public APIs
                 Key: KAFKA-16604
                 URL: https://issues.apache.org/jira/browse/KAFKA-16604
             Project: Kafka
          Issue Type: Improvement
            Reporter: Sagar Rao


Currently, one can create ConfigKey by either invoking the public constructor directly and passing it to a ConfigDef object or by invoking the a bunch of define methods. The 2 ways can get confusing at times. Moreover, it could lead to errors as was noticed in KAFKA-16592

We should ideally have only 1 way exposed to the users which IMO should be to create the objects only through the exposed define methods. This ticket is about marking the public constructor of ConfigKey as Deprecated first and then making it private eventually.



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