thetumbled opened a new issue, #21254: URL: https://github.com/apache/pulsar/issues/21254
### Search before asking - [X] I searched in the [issues](https://github.com/apache/pulsar/issues) and found nothing similar. ### Motivation The concept of group in Kafka is independent of the topic, while Pulsar's group/subscription seems to be a concept below the topic. Every `Subscription` corresponds to only one topic. ``` public class PersistentSubscription extends AbstractSubscription implements Subscription { protected final PersistentTopic topic; protected final ManagedCursor cursor; protected final String topicName; protected final String subName; ``` But when doing permission control, the sub belongs to the namespace instead of topic. Subscriptions with same name in the same namespace, but from different topics are treated as one subscription for permission control, and the role list is saved on zk under the path `/admin/policies/tenant/namespace`. ### Solution Move the role list for subscription to topic policy, so that the permission control for subscription is topic specific. ### Alternatives _No response_ ### Anything else? _No response_ ### Are you willing to submit a PR? - [X] I'm willing to submit a PR! -- 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. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
