[
https://issues.apache.org/jira/browse/KAFKA-10623?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kowshik Prakasam updated KAFKA-10623:
-------------------------------------
Summary: [Easy] Refactor code to avoid discovery conflicts for
classes:{Supported|Finalized}VersionRange (was: Refactor code to avoid
discovery conflicts for classes:{Supported|Finalized}VersionRange)
> [Easy] Refactor code to avoid discovery conflicts for
> classes:{Supported|Finalized}VersionRange
> -----------------------------------------------------------------------------------------------
>
> Key: KAFKA-10623
> URL: https://issues.apache.org/jira/browse/KAFKA-10623
> Project: Kafka
> Issue Type: Sub-task
> Reporter: Kowshik Prakasam
> Priority: Minor
>
> This Jira suggests changing few existing class names to avoid class discovery
> conflicts. Particularly the following classes:
> {code:java}
> org.apache.kafka.clients.admin.{Supported|Finalized}VersionRange{code}
> conflict with
>
>
> {code:java}
> org.apache.kafka.common.feature.{Supported|Finalized}VersionRange{code}
> The former is internal facing, while the latter is external facing (since it
> is used in the Admin#describeFeatures API). So, the internal facing classes
> can be renamed suitably. Possible alternative naming suggestions:
>
>
> {code:java}
> org.apache.kafka.clients.admin.{Supported|Finalized}Versions
> {code}
> {code:java}
> org.apache.kafka.clients.admin.Broker{Supported|Finalized}Versions
> {code}
> {code:java}
> org.apache.kafka.clients.admin.Broker{Supported|Finalized}VersionRange{code}
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
