e precedence over less specific
> patterns
> > > > > 3. for patterns of the same precedence DENY overrides ALLOW
> > > > >
> > > > > Determining specificity:
> > > > >
> > > > > Specificity is based on the Levenshtein distance between the
> pattern
> > and
>
Hello,
I'd like to propose a suggestion to our resource patterns in Kafka ACLs.
Currently, when adding new ACLs in Kafka, we have two types of resource
patterns for topics:
- LITERAL
- PREFIXED
However, when it comes to listing or removing ACLs, we have a couple more
options:
- MATCH
Hello,
I'd like to propose a suggestion to our resource patterns in Kafka ACLs.
Currently, when adding new ACLs in Kafka, we have two types of resource
patterns for topics:
- LITERAL
- PREFIXED
However, when it comes to listing or removing ACLs, we have a couple more
options:
- MATCH
Hello,
I'd like to propose a suggestion to our resource patterns in Kafka ACLs.
Currently, when adding new ACLs in Kafka, we have two types of resource
patterns for topics:
- LITERAL
- PREFIXED
However, when it comes to listing or removing ACLs, we have a couple more
options:
- MATCH