Is it OK if multiple different production customers share the same namespace prefix?
For example, does customer John Brown having namespace prefix nsJB conflict with customer Jenny Black also having namespace prefix nsJB?
With the current topology choices, it is not a safe thing. It means that those two customers have the potential for naming collisions if they happen to be assigned to the same infrastructure. Ownership is not based on the namespace - that’s in the tenant striping - but the tenant-owned objects are co-located in the same schema as things are currently arranged.
It is my/our intention to break that co-location arrangement, which would also remove the potential for name collisions. But that intention is directional, not imminent. Therefore namespace uniqueness between tenants remains essential for name uniqueness overall.
Thank you @kendra.b!
What is the course of action if this has already happened? Can something programmatically be done to preserve the data/configuration in the account if the namespace needs changed?
Had an internal discussion about this and I’m going to walk back my answer. Uniqueness in the storage (db) includes the tenant stripe. And the tenant stripe is unconditionally included in every query. So we can have two tenants with the same namespace and same metadata name stored in the same store and that causes no negative consequences.
2 Likes