# Hive Metastore

Feature only supported for GCP & AWS deployments (GCS & S3 metastore)

## Creating a connection

To set up a connection to Hive Metastore, provide the following:

* **Thrift URI**: The Thrift URI used to connect to the Hive Metastore using the Thrift protocol.
* **Location Type**: The type of storage where physical data files are present — **GCS** or **S3**.
* **Catalog Type**: Choose **HIVE** for a standard Hive catalog, or **ICEBERG** for an Iceberg catalog hosted in Hive Metastore.

### GCS credentials

<figure><img src="/files/Af1v0kGcgGEwy2OoIxKR" alt="Hive Metastore Create Connection — GCS"><figcaption><p>GCS location type</p></figcaption></figure>

| Field          | Description                    |
| -------------- | ------------------------------ |
| Client Email   | Service account email address  |
| Client ID      | Service account client ID      |
| Project ID     | GCP project ID                 |
| Private Key ID | Service account private key ID |
| Private Key    | Service account private key    |

*The specified GCS service account credentials should have read-access to the Hive Metastore warehouse. In the case of a private cloud deployment, write-access to the Telmai internal storage bucket must also be granted to this service account.*

### S3 credentials

<figure><img src="/files/VqaT9vuTd7sEJCQV8Rr5" alt="Hive Metastore Create Connection — S3"><figcaption><p>S3 location type</p></figcaption></figure>

| Field      | Description                               |
| ---------- | ----------------------------------------- |
| Region     | AWS region where the S3 bucket is located |
| Access Key | AWS access key ID                         |
| Secret Key | AWS secret access key                     |

## Connecting an asset

Once a connection is defined, you can start using it to create assets. To create assets, you will need:

* Database name
  * The next step will show you available tables

{% hint style="warning" %}
Group scans are not supported for Hive Metastore connections.
{% endhint %}


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.telm.ai/telmai/connect-to-data/data-connections/iceberg.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.