pulsar-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From GitBox <...@apache.org>
Subject [GitHub] yush1ga opened a new issue #893: Avoid confliction of subscription names for multiple tenants
Date Thu, 01 Jan 1970 00:00:00 GMT
yush1ga opened a new issue #893: Avoid confliction of subscription names for multiple tenants
URL: https://github.com/apache/incubator-pulsar/issues/893
 
 
   A topic of Pulsar can be used by multiple tenants.
   They have to be careful not to make a subscription name conflict.
   
   I propose 2 factors for namespace policies.
   
   ### 1. Subscription prefix
   When `subscription_prefix` in a namespace policy is `true` and `AuthenticationEnabled`
in `broker.conf` is `true`, subscription names for the namespace will be converted from `${ClientDefinedSubscriptionName}`
to `${AuthRroleName}-${ClientDefinedSubscriptionName}` automatically in broker.
   
   ### 2. Reserved subscription name
   Add settings to name space policies like following.
   ```
   reserved_subscription_name: {
       sub1: [role1],
       sub23: [role2, role3]
   }
   ```
   In this case, `sub1` can be used by only `role1` and `sub23` can be used by only `role2`and
`role3`.
   
   I think we can include both features in Pulsar.

----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
users@infra.apache.org


With regards,
Apache Git Services

Mime
View raw message