[
https://issues.apache.org/jira/browse/KAFKA-9392?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17015077#comment-17015077
]
ASF GitHub Bot commented on KAFKA-9392:
---------------------------------------
rajinisivaram commented on pull request #7956: KAFKA-9392; Clarify deleteAcls
javadoc and add test for create/delete timing
URL: https://github.com/apache/kafka/pull/7956
Follow-on from PR #7911 to clarify the guarantee for deleteAcls and add a
deterministic test to ensure we don't regress.
### Committer Checklist (excluded from commit message)
- [ ] Verify design and implementation
- [ ] Verify test coverage and CI build status
- [ ] Verify documentation (including upgrade notes)
----------------------------------------------------------------
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.
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
> Document and add test for deleteAcls that match single/multiple resources
> -------------------------------------------------------------------------
>
> Key: KAFKA-9392
> URL: https://issues.apache.org/jira/browse/KAFKA-9392
> Project: Kafka
> Issue Type: Task
> Components: security
> Reporter: Rajini Sivaram
> Assignee: Rajini Sivaram
> Priority: Major
> Fix For: 2.5.0
>
>
> From PR review of
> [https://github.com/apache/kafka/pull/7911:|https://github.com/apache/kafka/pull/7911,]
> If you do {{Admin.createAcls()}} followed by {{Admin.deleteAcls()}}, if you
> specify the ACL in both cases, you are guaranteed to delete the ACL
> regardless of which broker handles the request. If you use a matching filter
> that doesn't specify the resource pattern for {{deleteAcls}}, then we don't
> provide that guarantee.
> We should document this and add a deterministic test for the guaranteed
> behaviour to ensure we don't regress.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
