You are viewing a plain text version of this content. The canonical link for it is here.
Posted to jira@kafka.apache.org by "Satish Duggana (Jira)" <ji...@apache.org> on 2021/05/10 10:57:00 UTC

[jira] [Updated] (KAFKA-12757) Move server related common and public classes into separate modules.

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

Satish Duggana updated KAFKA-12757:
-----------------------------------
    Summary: Move server related common and public classes into separate modules.  (was: Move server related common classes into a separate `server-common` module.)

> Move server related common and public classes into separate modules.
> --------------------------------------------------------------------
>
>                 Key: KAFKA-12757
>                 URL: https://issues.apache.org/jira/browse/KAFKA-12757
>             Project: Kafka
>          Issue Type: Improvement
>            Reporter: Satish Duggana
>            Priority: Major
>
> There are two sets of classes that we want to pull out here for server common/api classes.
> 1. All the common classes used by server modules.
> 2. All the public server side classes exposed to users. Some of these classes are storage-api, security, quotas etc.
> Couple of approaches that we can consider here:
> 1. Both sets of classes will be added in server-common module but common classes will have a package prefix as org.apache.kafka.server.common. But public classes will continue to have the existing package names. We will generate javadocs for these public classes.
> 2. Common classes used by server modules will be added in server-common module. We will create another module called server-api for server side public classes.
> Pl feel free to add if you want to discuss other approaches in modularizing these classes. 
>  



--
This message was sent by Atlassian Jira
(v8.3.4#803005)