# Hive Native Permissions

Source: https://userguide.qualytics.io/source-datastore/datastore/native/hive/deep-dive/permissions/

Two separate things have to be granted before someone can put a Hive Native datastore to work, and they are granted in different places:

- **On your Hive cluster**, the identity Qualytics connects with needs read access to the metastore and to the table files. Without it the connection cannot read your data at all.
- **In Qualytics**, the person doing the work needs a user role and a team permission. Without them the datastore exists but they cannot create, change, or run operations on it.

The rest of this page covers both, in that order.

---

## Access on your Hive Cluster

Because Hive Native reads the data files themselves, it needs more than a working metastore connection. Reaching the metastore alone is enough to list databases and tables, and a datastore set up that way syncs successfully and then fails the first time it tries to profile or scan. Grant the access below before the first operation, not after.

Qualytics never writes to Hive through this connector, so read access is all it asks for.

### What the connection needs

| Access | Purpose |
| --- | --- |
| Read the metastore | Databases, tables, columns, and the location of every table and partition |
| Read the table's files and directories | The data itself, during profile and scan operations |

On HDFS, file access is checked against the identity Qualytics presents. An identity that can list tables but cannot read the warehouse directory produces exactly the failure described above: a clean sync, then an error on the first profile.

### Network access

Allow your Qualytics deployment to reach the services below. The **Add Datastore** form shows the addresses your connections originate from, under **Public addresses** and **Private addresses**, so you can copy the ones that match your network setup into your security groups or firewall rules.

| Service | Typical port | Why it is needed |
| --- | --- | --- |
| Hive metastore | 9083 | Databases, tables, columns, and partition locations |
| Key Distribution Center (KDC) | 88 | Kerberos tickets |
| HDFS NameNode | 8020 | File listings, block locations, and delegation tokens. With high availability, allow both NameNodes |
| HDFS DataNodes | 1004, or 9866 | The data itself |
| Key Management Server (KMS) | 9494 (HTTPS) | Only when tables live in an HDFS encryption zone. See [Encryption zones](https://userguide.qualytics.io/source-datastore/datastore/native/hive/deep-dive/how-it-works/#encryption-zones) |

The DataNode port differs by cluster. Secured clusters commonly use the privileged port 1004, while unsecured clusters commonly use 9866. Check `dfs.datanode.address` on your cluster if you are unsure.

No HDFS web UIs, WebHDFS, HttpFS, Cloudera Manager, Ranger admin, or SSH access is needed. [How Hive Native Works](https://userguide.qualytics.io/source-datastore/datastore/native/hive/deep-dive/how-it-works/) shows which step of a read uses each service.

> **Tip: Tables in cloud object storage**
>
> If your Hive tables are stored in Amazon S3, Azure Data Lake Storage, or Google Cloud Storage rather than in HDFS, you only need the metastore and the KDC. Qualytics reads object storage with the credentials your deployment is already configured with, so no NameNode or DataNode access is required.

### Hostname resolution

Table and partition locations recorded in the metastore usually name hosts rather than IP addresses, for example `hdfs://hive-primary.internal:8020/warehouse/sales`. Qualytics follows those locations exactly as the metastore reports them, so every hostname they contain has to resolve from your Qualytics deployment. If a name resolves only inside the cluster, add the records to the DNS your deployment uses.

This is the most common reason a connection that tested successfully cannot read data: the metastore was reachable by its own address, and the storage hosts it named were not.

### Kerberos permissions

The identity Qualytics presents through its keytab needs the same two kinds of access listed above: read on the Hive databases and tables you want to monitor, and read on their files in storage. Granting it on the metastore alone is not sufficient.

If the tables live in an HDFS encryption zone, the identity also needs **Decrypt EEK** on the zone key in your KMS policies. No other KMS permission is required. See [Encryption zones](https://userguide.qualytics.io/source-datastore/datastore/native/hive/deep-dive/how-it-works/#encryption-zones).

See [Hive Native Authentication](https://userguide.qualytics.io/source-datastore/datastore/native/hive/deep-dive/authentication/) for which identity is which, and where each one is entered on the connection.

---

## Permissions in Qualytics

Qualytics checks two layers, and an action is allowed only when both pass.

- **User roles** are workspace-wide: **Member**, **Manager**, and **Admin**.
- **Team permissions** are granted per datastore through the teams a user belongs to: **Reporter**, **Viewer**, **Drafter**, **Author**, and **Editor**.

For the full reference, see [User Roles](https://userguide.qualytics.io/settings/access/users/roles/overview/) and the [Team Permissions Overview](https://userguide.qualytics.io/settings/access/teams/team-permissions/overview/).

### User Roles

| Action | Member | Manager | Admin |
| --- | --- | --- | --- |
| View the datastore and its activity | Allowed | Allowed | Allowed |
| Create a Hive Native datastore | Not allowed | Allowed | Allowed |
| Edit the datastore's settings | Allowed | Allowed | Allowed |
| Run and schedule Sync, Profile, and Scan | Allowed | Allowed | Allowed |
| Link an enrichment destination | Allowed | Allowed | Allowed |
| Unlink an enrichment destination | Not allowed | Not allowed | Allowed |
| Delete the datastore | Not allowed | Not allowed | Allowed |

### Team Permissions

Checked on the datastore itself, in addition to the user role above.

| Action | Reporter | Viewer | Drafter | Author | Editor |
| --- | --- | --- | --- | --- | --- |
| View the datastore and its activity | Allowed | Allowed | Allowed | Allowed | Allowed |
| Preview the datastore's data | Not allowed | Allowed | Allowed | Allowed | Allowed |
| Edit the datastore's settings | Not allowed | Not allowed | Not allowed | Not allowed | Allowed |
| Run and schedule Sync, Profile, and Scan | Not allowed | Not allowed | Not allowed | Not allowed | Allowed |
| Link an enrichment destination | Not allowed | Not allowed | Not allowed | Not allowed | Allowed |

### How the two layers meet

To **create** a Hive Native datastore, a user needs the **Manager** role. Team permissions are not consulted, because the datastore does not exist yet.

To **edit** it, **run an operation** on it, or **link an enrichment destination**, a user needs the **Member** role or higher *and* the **Editor** team permission on that datastore, through at least one of the teams the datastore belongs to.

To **delete** it, or to **unlink** its enrichment destination, a user needs the **Admin** role. No team permission is consulted.

> **Info: Admins bypass team permissions**
>
> A user with the **Admin** role passes every team permission check, on any datastore, whether or not they belong to a team that owns it.

> **Tip: Who should hold what**
>
> Give the **Editor** team permission to the people who own the Hive datastores day to day, since it is what gates running a Sync after a schema change. Reserve the **Manager** role for whoever onboards new clusters, and the **Admin** role for the few people who should be able to remove a datastore.

---

## See Also

- **How It Works**

  One read from start to finish: the services Qualytics reaches, on which ports, and where your cluster's policies apply.

  [How It Works](https://userguide.qualytics.io/source-datastore/datastore/native/hive/deep-dive/how-it-works/)
- **Authentication**

  Kerberos on this connector: the service principal, the keytab Qualytics presents, and the `krb5.conf` that reaches the realm.

  [Authentication](https://userguide.qualytics.io/source-datastore/datastore/native/hive/deep-dive/authentication/)
- **Examples**

  Worked scenarios: a partitioned Parquet warehouse, a database of mixed formats, object storage, and two Kerberized clusters.

  [Examples](https://userguide.qualytics.io/source-datastore/datastore/native/hive/deep-dive/examples/)
- **Best Practices**

  Recommendations for planning the connection, splitting tables between the two Hive connectors, and keeping operations fast.

  [Best Practices](https://userguide.qualytics.io/source-datastore/datastore/native/hive/deep-dive/best-practices/)

*Last updated: November 7, 2026.*
