Hello, Now that we have started to think about Pulsar 3.0, let me share another long standing feature that can be implemented mostly only with such big changes that would deserve a major version bump.
Currently every object managed by Pulsar is directly handled and referred using a logical, human readable name: - tenants - namespaces - topics - functions/sinks/sources This fact is limiting some interesting use case: - renaming objects (you cannot rename a topic for instance) - safe delete/recreate (clients may connect to the new version of the same object, but now it has a different meaning) - aliasing (giving multiple logical names to the same thing) Additionally it would be great to have the ability to not have globally unique tenant names, but allow that a tenant name is a logical name and its meaning depends on the user that authenticated: now in a big multi-tenant environment you cannot have multiple tenants with the same name, so if you are providing Pulsar as SaaS, all of your customer cannot use the same "tenant name". You cannot even have two tenants named "test-tenant" or "demo". I am not proposing here solutions for this problem, even if I already have some ideas, but I want to open this discussion and understand if others on the community would like to work on these kind of problems Cheers Enrico
