[
https://issues.apache.org/jira/browse/KAFKA-15318?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Colin McCabe updated KAFKA-15318:
---------------------------------
Description: On the controller, move publishing acls to the authorizer into
a dedicated MetadataPublisher, AclPublisher. This publisher listens for
notifications from MetadataLoader, and receives only committed data. This
brings the controller side in line with how the broker has always worked. It
also avoids some ugly code related to publishing directly from the
QuorumController. Most important of all, it clears the way to implement
metadata transactions without worrying about Authorizer state (since it will be
handled by the MetadataLoader, along with other metadata image state). (was:
On the controller, move Acl publishing into a dedicated MetadataPublisher,
AclPublisher. This publisher listens for notifications from MetadataLoader, and
receives only committed data. This brings the controller side in line with how
the broker has always worked. It also avoids some ugly code related to
publishing directly from the QuorumController. Most important of all, it clears
the way to implement metadata transactions without worrying about Authorizer
state (since it will be handled by the MetadataLoader, along with other
metadata image state).)
> Update the Authorizer using AclPublisher
> ----------------------------------------
>
> Key: KAFKA-15318
> URL: https://issues.apache.org/jira/browse/KAFKA-15318
> Project: Kafka
> Issue Type: Bug
> Reporter: Colin McCabe
> Priority: Major
>
> On the controller, move publishing acls to the authorizer into a dedicated
> MetadataPublisher, AclPublisher. This publisher listens for notifications
> from MetadataLoader, and receives only committed data. This brings the
> controller side in line with how the broker has always worked. It also avoids
> some ugly code related to publishing directly from the QuorumController. Most
> important of all, it clears the way to implement metadata transactions
> without worrying about Authorizer state (since it will be handled by the
> MetadataLoader, along with other metadata image state).
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
