Page History

...

• Create a topic with a user that isn’t part of a virtual cluster: everything stays the same as it is currently.
• Create a topic with a user that is already assigned to a virtual cluster: topics that are created within a virtual cluster would have generated names, where one part continues to be the user-given name while another part is unique. This would be implemented by prefixing the UUID of the topic to the topic. This way we would form topic names in the UUID.topicname form, for instance e58ed763-928c-4155-bee9-fdbaaadc15f3.mytopic. This is needed to avoid conflicting names between virtual clusters. Links would also have names with the user-given topic name being the default, to be able to identify them in a user-friendly way. Also links having names would accommodate use-cases when users share topics between virtual clusters as they can opt to use a different name if they conflict in different virtual clusters.

The UUID based mechanism would fulfill all requirements:

• Makes a valid topic name as the string representation of the UUID is a valid topic name. We considered base64 encoding as it's shorter, but it also may contain invalid characters for topic names.
• The string representation of the topic name is 36 characters,  the overall topic name will still likely fit the 249 maximum limit.
• The generated topic name still has a human-readable part, so it's easier to identify its original purpose.

Deleting Topics

Deleting topics in virtual clusters would simply mean deleting the links. If all links are deleted, then the topic doesn’t belong to any virtual cluster, so administrators would simply need to delete the topic to get rid of it forever. Deleting the physical topic wouldn’t be allowed as long as there are links pointing to it. This is necessary to prevent dangling links.

...