[
https://issues.apache.org/jira/browse/KAFKA-7010?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andy Coates updated KAFKA-7010:
-------------------------------
Description:
Following on from the PR [#5117|[https://github.com/apache/kafka/pull/5117]...]
and discussions with Colin McCabe...
The current ResourceNameType.ANY may be misleading as it performs pattern
matching for wildcard and prefixed bindings. Where as ResourceName.ANY just
brings back any resource name.
Renaming to ResourceNameType.MATCH and adding more Java doc should clear this
up.
Finally, ResourceNameType is no longer appropriate as the type is used in
ResourcePattern and ResourcePatternFilter. Hence rename to PatternType.
was:
Following on from the PR [#5117|[https://github.com/apache/kafka/pull/5117]...]
and discussions with Colin McCabe...
The current ResourceNameType.ANY may be misleading as it performs pattern
matching for wildcard and prefixed bindings. Where as ResourceName.ANY just
brings back any resource name.
Renaming to ResourceNameType.MATCH and adding more Java doc should clear this
up.
> Rename ResourceNameType.ANY to MATCH
> ------------------------------------
>
> Key: KAFKA-7010
> URL: https://issues.apache.org/jira/browse/KAFKA-7010
> Project: Kafka
> Issue Type: Sub-task
> Components: core, security
> Reporter: Andy Coates
> Assignee: Andy Coates
> Priority: Major
> Fix For: 2.0.0
>
>
> Following on from the PR
> [#5117|[https://github.com/apache/kafka/pull/5117]...] and discussions with
> Colin McCabe...
> The current ResourceNameType.ANY may be misleading as it performs pattern
> matching for wildcard and prefixed bindings. Where as ResourceName.ANY just
> brings back any resource name.
> Renaming to ResourceNameType.MATCH and adding more Java doc should clear this
> up.
> Finally, ResourceNameType is no longer appropriate as the type is used in
> ResourcePattern and ResourcePatternFilter. Hence rename to PatternType.
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
