# Catalogs

Most analytical data is stored in cloud object stores like Amazon S3, GCS, or Azure Blob Storage. However, structural metadata such as table names, schemas, and partitions managed by metastores like Hive, AWS Glue, Dataproc Metastore, Unity Catalog, or Apache Polaris.

In e6data, a Catalog connects to these metastores to provide the metadata needed for querying data stored in object stores efficiently.

| Catalog Service                                                                         | Description                                                      |
| --------------------------------------------------------------------------------------- | ---------------------------------------------------------------- |
| [**Hive Metastore**](/product-documentation/catalogs/create-catalogs/hive-metastore.md) | Traditional metastore widely used with Hadoop and Spark.         |
| [**Glue Metastore**](/product-documentation/catalogs/create-catalogs/glue-metastore.md) | AWS-managed metastore with schema versioning and S3 integration. |
| [**Unity Catalog**](/product-documentation/catalogs/create-catalogs/unity-catalog.md)   | Databricks’ unified metadata and governance layer.               |
| [**Apache Polaris**](/product-documentation/catalogs/create-catalogs/apache-polaris.md) | REST-based Iceberg catalog for scalable metadata management.     |

{% hint style="info" %}
Cross-account support requires specific IAM configuration depending on the cloud provider.
{% 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.e6data.com/product-documentation/catalogs.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.