> For the complete documentation index, see [llms.txt](https://docs.e6data.com/query-engine/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.e6data.com/query-engine/guides/catalogs/apache-polaris.md).

# Apache Polaris

Apache Polaris is an open-source, cloud-native catalog service for managing Apache Iceberg catalogs. With e6data, Polaris lets you query structured and semi-structured data across cloud data lakes through a unified interface, with support for schema evolution, nested namespaces, and metadata access over the Apache Iceberg REST protocol.

## Before you start

* Have your **Polaris Host** URL ready.
* Have a **Client ID** and **Client Secret** for OAuth-based authentication.
* For Serverless workspaces, complete the cloud-specific storage access setup.
* For cross-account configurations, have the relevant cloud identity values ready.

## Connect to Apache Polaris

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.
3. Select **Catalog Type** as **Apache Polaris**.
4. (Optional) Enable **Governance**. Apply fine-grained access control using Ranger, OPA, Unity, or Lake Formation.
5. Provide the Polaris connection details:

   | Field             | Description                                                   |
   | ----------------- | ------------------------------------------------------------- |
   | **Polaris Host**  | The Polaris server URL (for example, `polaris.mycompany.com`) |
   | **Client ID**     | OAuth client ID for Polaris authentication                    |
   | **Client Secret** | OAuth client secret                                           |
6. (Optional) Enable **Cross-Account Connection** if accessing data across cloud accounts or tenants. Provide the **Tenant ID** (Azure), the **Client ID** that has access to the data, and the **Storage Account Name**.
7. Click **Test Connection** to verify connectivity. The form validates that a catalog name and Polaris Host are provided.
8. After a successful test, **specify the schemas to include**.
9. Click **Create Catalog** to complete the setup.
10. (Optional) Click **Reset** at any time to clear all entered fields.

## Edit a Polaris catalog

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 Polaris catalog

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

* [Catalogs overview](/query-engine/guides/catalogs.md)
* [Iceberg REST Catalog](/query-engine/guides/catalogs/iceberg-rest-catalog.md)
* [Cross-account access](/query-engine/guides/catalogs/cross-account.md)


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## 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, and the optional `goal` query parameter:

```
GET https://docs.e6data.com/query-engine/guides/catalogs/apache-polaris.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.