[GitHub] [kafka] jsancio commented on a diff in pull request #12146: MINOR: Remove kraft authorizer from list of missing features

[GitBox <gi...@apache.org>]

jsancio commented on code in PR #12146:
URL: https://github.com/apache/kafka/pull/12146#discussion_r870457817


##########
config/kraft/README.md:
##########
@@ -114,9 +114,7 @@ We don't support any kind of upgrade right now, either to or from KRaft mode.  T
 
 Finally, the following Kafka features have not yet been fully implemented:
 
-* Support for certain security features: configuring a KRaft-based Authorizer, setting up SCRAM, delegation tokens, and so forth
-  (although note that you can use authorizers such as `kafka.security.authorizer.AclAuthorizer` with KRaft clusters, even
-  if they are ZooKeeper-based: simply define `authorizer.class.name` and configure the authorizer as you normally would).
+* Support for certain security features: setting up SCRAM, delegation tokens, and so forth.
 * Support for some configurations, like enabling unclean leader election by default or dynamically changing broker endpoints

Review Comment:
   No. This is referring to supporting unclean leader election through configuration. Unclean leader election using the configuration `unclean.leader.election.enable` is not yet supported in KRaft. KRaft only supports unclean leader election through the `ElectLeaders` RPC.
   
   KIP-704 was about propagating the fact that unclean leader election was performed to the topic partition replicas so they can recover from this. We plan to use this to recover from pending transactions.



-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: jira-unsubscribe@kafka.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org