Aman Singh created KAFKA-13983:
----------------------------------
Summary: Support special character in Resource name in ACLs
operation by sanitizing
Key: KAFKA-13983
URL: https://issues.apache.org/jira/browse/KAFKA-13983
Project: Kafka
Issue Type: Improvement
Components: core
Reporter: Aman Singh
Currently, resource names in ACLS can contain any special characters, but
resource names with some special characters are not a valid zookeeper path
entry.
For example resource name {{test/true}} is not a valid zookeeper path entry.
Zookeeper will create a child node, name as {color:#de350b}{{true}}{color}
inside the {color:#de350b}{{test}}{color} node.
This will create two problems:-
# If there is *one* ACL with a resource name {{test}} it can't be deleted
because if there is only one, Kafka tries to delete the node as well by
thinking it will be empty which is not true it has the child node {{true.}}
# When broker restarts {{{}ACL cache{}}}(which is used for ACL operations like
describe, authorization etc) update from zookeeper and Kafka only looks for
ACLs that are direct child nodes of resource type in the ACL tree.
--
This message was sent by Atlassian Jira
(v8.20.7#820007)
