Is it possible to change the is_global_namespace flag for a namespace?

Once a namespace is created, it cannot change the “is_global_namespace” flag, so if you have an existing namespace that was created as non-global, you are out of luck.

  • Is there any way around this?
  • What would happen if you changed the flag in the database itself?
  • Is there a drawback to create all namespaces as global? You can do it even if you only have a single entry in clusterInformation (the only requirement is enableGlobalNamespace: true)
  • Can you change the (enableGlobalNamespace: true) flag on an already-running cluster (even if it means cycling temporal).

Thanks a lot!

  • Is there any way around this?

we are planning allowing turning local namespace to global namespace
@Yimin_Chen about ETA & progress

  • What would happen if you changed the flag in the database itself?

i guess some basic contract will be broken (undefined behavior on server)

  • Is there a drawback to create all namespaces as global? You can do it even if you only have a single entry in clusterInformation (the only requirement is enableGlobalNamespace: true)

assuming configuration is current, history server will start additional goroutines for xdc (passive task processing, e.g.), wasting some resources (maybe ok to you?)

  • Can you change the (enableGlobalNamespace: true) flag on an already-running cluster (even if it means cycling temporal).

this will enable history service to start additional goroutines managing fetching & processing tasks for xdc. this turn up (turn on?) is not well tested btw (entire xdc is experimental)

all in all, we are currently working on improving xdc, details @Yimin_Chen