You are viewing a plain text version of this content. The canonical link for it is here.
Posted to jira@kafka.apache.org by "Jason Gustafson (Jira)" <ji...@apache.org> on 2021/02/19 01:07:00 UTC
[jira] [Resolved] (KAFKA-12278) Keep api versions consistent with
api scope
[ https://issues.apache.org/jira/browse/KAFKA-12278?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jason Gustafson resolved KAFKA-12278.
-------------------------------------
Resolution: Fixed
> Keep api versions consistent with api scope
> -------------------------------------------
>
> Key: KAFKA-12278
> URL: https://issues.apache.org/jira/browse/KAFKA-12278
> Project: Kafka
> Issue Type: Improvement
> Reporter: Jason Gustafson
> Assignee: Jason Gustafson
> Priority: Major
>
> With KIP-500, some APIs are only accessible by the broker and some are only accessible by the controller. We need a better way to indicate the scope of the API so that we can keep it consistent with the `ApiVersions` API. Basically we have the following scopes:
> - zk broker (e.g. LeaderAndIsr)
> - kip-500 broker (e.g. DecommissionBroker)
> - kip-500 controller (e.g. Envelope)
> These categories are not mutually exclusive. For example, the `Fetch` API must be exposed in all scopes. We could go even further by distinguishing an inter-broker scope, but that is probably not needed for now.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)