Add a Hive Native Datastore with a New Connection
This page walks you through adding a Hive Native source datastore while creating its connection: every field the form asks for, section by section, followed by the steps to test and finish.
Once the datastore is created, run a Sync to discover the tables in the selected database. Tables that Hive Native declines to read, such as views and transactional tables, are reported individually while the rest of the database syncs normally.
Already have a connection?
To add a Hive Native datastore on a connection that already exists, go to Add with an Existing Connection.
Before you start, review the Hive Native Permissions and the Authentication page. Reaching the metastore is not enough on its own: the connection also needs to reach the storage the metastore points at.
Warning
Hive Native cannot be used as an enrichment datastore. After you add it as a source, link a separate enrichment datastore as its destination to store anomalies and metadata: either during creation or afterwards.
Field reference
After you choose New Connection, the form shows three sections. Connection Properties holds everything that belongs to the connection, including the Secrets Management and Authentication groups inside it. Location holds the database to monitor, and General holds the datastore's own settings.
Connection Properties
These fields define the metastore Qualytics connects to. They belong to the connection, so they can be reused by other datastores later. Secrets Management and Authentication, described next, sit inside this section.
| Field | Required | Type | Description |
|---|---|---|---|
| Connection Name | Text | A label for the saved connection (e.g., acme_hive_metastore), so other datastores can reuse it later. |
|
| Metastore URI | Text | The address of the Hive metastore, in the form thrift://metastore-host:9083. For a highly available metastore, list each address separated by commas. |
|
| Warehouse Directory | Text | The warehouse root, for example /user/hive/warehouse. Optional, and not needed for reading: Qualytics takes each table's location from the metastore rather than from a warehouse root. |
No Catalog field
Connectors such as Athena ask for a Catalog, the level above the database. Hive has no such level, only databases and tables, so the form does not ask for one. Qualytics works the rest out from the metastore address.
Authentication
Shown inside Connection Properties. Hive Native authenticates with Kerberos. See Hive Native Authentication for which identity belongs in which field.
| Field | Required | Type | Description |
|---|---|---|---|
| Type | Option | Kerberos, the only available option. The metastore protocol has no user and password authentication of its own. | |
| Service Principal | Text | The metastore's service principal, for example hive/_HOST@DOMAIN.COM. The _HOST portion is replaced with the metastore's own hostname. This identifies the metastore, not your account. |
|
| Keytab | File | The keytab holding the key for the identity Qualytics should present. Must be named with a .keytab extension. Stored encrypted and never displayed back. Leave it empty to use the Kerberos credentials configured on the deployment. |
|
| krb5.conf | File | The Kerberos configuration for the cluster's realm, so Qualytics can reach its Key Distribution Center. Leave it empty to use the deployment's configuration. |
Secrets Management
Also inside Connection Properties, and optional. Use it only if you want Qualytics to pull credentials from a secrets manager instead of typing them into the form. Turn on HashiCorp Vault to show the fields below. Despite the label, any secrets manager that exposes a compatible REST API works; see Secrets Management.
| Field | Required | Type | Description |
|---|---|---|---|
| Login URL | Text | The Vault endpoint Qualytics uses to authenticate (e.g., https://vault.example.com/v1/auth/approle/login). |
|
| Credentials Payload | Text | A JSON body containing the credentials Vault expects (e.g., {"role_id":"...","secret_id":"..."}). |
|
| Token JSONPath | Text | The JSONPath that extracts the client token from Vault's response. Defaults to $.auth.client_token. |
|
| Secret URL | Text | The Vault path where the secret is stored (e.g., https://vault.example.com/v1/secret/data/hive). |
|
| Token Header Name | Text | The HTTP header name used to send the token. Defaults to X-Vault-Token. |
|
| Data JSONPath | Text | The JSONPath that extracts the secret payload from Vault's response. Defaults to $.data. |
Location
Pick the Hive database Qualytics should read from. Unlike Connection Properties, this section belongs to the datastore rather than to the connection, so it is filled in on both flows.
| Field | Required | Type | Description |
|---|---|---|---|
| Database | Option | One or more Hive databases to monitor. The dropdown is filled in once Qualytics connects to the metastore. Each database you pick becomes its own Qualytics datastore. |
General
The datastore's own settings.
| Field | Required | Type | Description |
|---|---|---|---|
| Name | Text | The datastore name in Qualytics. Comes suggested from the connection name and the database, so you can leave it blank to accept that suggestion. | |
| Group | Option | Organizes your datastores under a shared group in the navigation tree. Select an existing group, or turn on Add New Group to create one. | |
| Teams | Option | Select one or more teams to associate with this source datastore. | |
| Initiate Sync | Checkbox | Ask Qualytics to run the first Sync for you once the datastore is created. You can always run a Sync yourself from the datastore afterwards. |
Selecting more than one database
When you pick several databases in Location, each one becomes its own datastore and Name is replaced by Name Template, a naming pattern applied to all of them. Use {{schema}} as the placeholder for the database name: hive_{{schema}} becomes hive_sales, hive_finance, and so on. Left empty, each datastore is named from the connection name and its database.
Below the form, an information banner lists the Public addresses and Private addresses your datastore connections originate from. Allow the ones that match your network setup through your security groups or firewall rules; see Permissions for the ports involved.
Steps
Step 1: Navigate to the Datastores page.
Step 2: Click the Add button at the top-right corner and choose Source from its menu.
Step 3: The Datastore step opens, the first of two.
Step 4: Select New Connection next to the Search field.
Step 5: Select Hive Native from the connector grid. Use the search field to filter connectors by name.
Step 6: Fill in the fields of Connection Properties, Authentication, Location, and General, as described in the Field reference.
Step 7: Click Test connection. A success message confirms that the connection has been verified.
Info
The Finish and Next buttons stay disabled until the connection test passes on the current values. If you change a connection field after a successful test, test again. If the test fails, see Troubleshooting.
Step 8: Click Finish to create the datastore.
Tip
To link an enrichment destination so Qualytics can store anomalies and metadata from the first operation, click Next instead of Finish. See Link Enrichment on Datastore Creation.
Step 9: A success dialog confirms that your datastore has been added. Click Go to your datastore to open its page.