[jira] [Updated] (KAFKA-13983) Fail the creation with "/" in resource name in zk ACL

["Aman Singh (Jira)" <ji...@apache.org>]

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

Aman Singh updated KAFKA-13983:
-------------------------------
    Summary: Fail the creation with "/" in resource name in zk ACL  (was: Support special character in Resource name in ACLs operation by sanitizing )

> Fail the creation with "/" in resource name in zk ACL
> -----------------------------------------------------
>
>                 Key: KAFKA-13983
>                 URL: https://issues.apache.org/jira/browse/KAFKA-13983
>             Project: Kafka
>          Issue Type: Bug
>          Components: core
>            Reporter: Aman Singh
>            Assignee: Aman Singh
>            Priority: Minor
>             Fix For: 3.3.0
>
>
> 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 {color:#de350b}{{test/true}} {color}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 {color:#de350b}{{test}}{color} 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 {{{color:#de350b}true{color}.}}
>  # When broker restarts {color:#de350b}{{ACL cache}}{color}(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.10#820010)