Polaris and Global Namespace Integration Support

Polaris and Global Namespace (GNS) integration provides support for multi-cluster analytics. This integration provides centralized governance, shared catalogs, and cross-cluster access without copying data.

The Polaris catalog service can store its catalog (that is, the catalog metadata) in a GNS path. This capability applies to GNS locations backed by MFS as well as to GNS locations backed by an Object Store, and in both cases Polaris supports these GNS-backed locations without requiring any additional configuration changes.

To use external NFS, the Polaris Aministrator must follow these steps:
  1. Add polaris.features."ENABLE_GNS_NFS_SUPPORT" to the application properties.
  2. Add "FILE" to polaris.features."SUPPORTED_CATALOG_STORAGE_TYPES".
    polaris.features."ENABLE_GNS_NFS_SUPPORT"=true
polaris.features."SUPPORTED_CATALOG_STORAGE_TYPES"=["FILE",MFS", "S3","GCS","AZURE"]
  3. Restart Polaris.

To control where an external GNS is mounted, Polaris uses the polaris.features."CATALOG_NFS_GNS_PREFIX" property. This property defines a list of NFS mount locations where the catalog can be created when using FILE storage. Each entry must be specified as an absolute file:/// URI (for example, file:///mnt/gns_cluster1), not as a plain filesystem path.

For example:
# polaris.features."CATALOG_NFS_GNS_PREFIX"=["file:///mnt/gns_cluster1", "file:///mnt/gns_cluster2"]