Skip to main content

​
Before you start

  • Have your Hive Metastore host and port ready.
  • Confirm network connectivity from your e6data workspace to the metastore (allow the metastore port through firewalls / NSGs).
  • For Serverless workspaces, complete the cloud-specific storage access setup so e6data can read the underlying data.
  • For cross-account or cross-tenant configurations, have the relevant cloud identity values ready.

​
Connect to Hive Metastore

  1. Navigate to the Catalogs section from the sidebar and click Create Catalog.
  2. Enter a Catalog Name. The name must be unique within the workspace. Lowercase letters, numbers, and hyphens are recommended (for example, azure-hive-catalog).
  3. Select Catalog Type as Hive Metastore.
  4. (Optional) Enable Governance. Apply fine-grained access control using Ranger, OPA, Unity, or Lake Formation. Use this if your organization enforces centralized data governance policies.
  5. Configure the metastore connection:
  6. (Optional) Enable Cross-Account Connection if the metastore or the underlying storage lives in a different cloud account or tenant. The fields differ by cloud - see Cross-account configuration below.
  7. Click Test Connection to verify connectivity and configuration.
  8. After a successful test, specify the schemas to include by selecting only the databases you want this catalog to expose.
  9. Click Create Catalog. The catalog appears in the catalogs list and is available to attach to clusters.

​
Cross-account configuration

If your metastore or storage is in a different cloud account or tenant, enable Cross-Account Connection and provide cloud-specific values. Azure - for a metastore where the storage account is in a different Azure tenant: AWS - for a metastore or storage in a different AWS account: The trust policy on the role must allow e6data’s identity to assume it. See AWS Hive Metastore cross-account for the full pattern.

​
Public Hive Metastore warning

If your Hive Metastore is hosted on a public IP (not in a private network), the create flow prompts you to acknowledge the security implications before proceeding. Hive’s Thrift protocol does not authenticate by default - running it on a public endpoint is a significant exposure. Prefer:
  • A private endpoint (VNet peering, VPC peering, or PrivateLink) over the public internet.
  • A reverse proxy that adds authentication in front of the Thrift port.
  • Cross-account access patterns that don’t require exposing the metastore publicly.

​
Edit a Hive Metastore connection

Editing a Hive Metastore connection lets you change the databases and schemas available for querying.
To change connection details (host, port, and so on), delete and recreate the connection.
  1. In the Catalogs section, click the catalog name to open its summary page.
  2. Click Edit Catalog at the top right.
  3. Select or deselect schemas as required.
  4. To enable automatic catalog updates, toggle on auto-refresh and set the desired interval; otherwise continue.
  5. Click Update Catalog.

​
Delete a Hive Metastore connection

  1. In the Catalogs section, click the name of the catalog you want to delete to open its summary page.
  2. Click Delete Catalog at the top right and confirm. The catalog is removed; clusters attached to it lose access.

​
See also

Last modified on October 1, 2026