Articles in this section

How to ship records to a different namespace via XDR

Context

Normally, XDR ships records from one namespace to the namespace of the same name in the remote DC. In most use cases, these are considered the "same" namespace and all is well. Some use cases may have a different set of namespaces on the destination cluster, so using the same namespace name is invalid.

Method

Set the remote-namespace configuration parameter in the dc/namespace subcontext on the source cluster to the name of the destination namespace on the destination DC.

Notes

Caveats:
  • This configuration can be set only when the remote DC is not connected.
  • To unset dynamically, use the null special keyword.
  • The value of remote-namespace cannot be the name of a local namespace.
  • The local namespace should not exist on the remote destination (if it does, only shipping to that namespace is supported, which is done without the use of this configuration parameter).
  • The value of remote-namespace must be unique across namespaces in the local DC (two or more namespaces in a cluster cannot map to the same remote namespace, but two different clusters can each map to the same namespace in a third cluster).
See the configuration reference page for details on setting this dynamically.

Applies To Earliest Version

5.2

Applies To Latest Version

Current Version
Was this article helpful?
0 out of 0 found this helpful