Catalog Type Reference
Each catalog type requires specific properties. The new catalog form pre-populates sensible defaults for the selected type. This page lists the complete property set for each type.
Hadoop
Catalogs backed by a Hadoop-compatible filesystem (HDFS).
| Property | Required | Description |
|---|---|---|
uri | Yes | HDFS nameservice URI, e.g. hdfs://nameservice1:8020 |
Supports Kerberos authentication for secured HDFS clusters.
Hive
Catalogs using Apache Hive Metastore via the Thrift protocol.
| Property | Required | Description |
|---|---|---|
uri | Yes | Thrift Metastore URI, e.g. thrift://metastore.example.com:9083 |
catalog | No | Catalog name, if the Metastore hosts multiple catalogs |
Supports Kerberos authentication. When Kerberos is enabled, Ice Flow automatically configures SASL transport for the Hive Metastore Thrift client.
Hive catalogs support continuous replication mode via the Metastore event stream.
JDBC
Catalogs stored in a relational database.
| Property | Required | Description |
|---|---|---|
uri | Yes | JDBC connection string, e.g. jdbc:postgresql://db.example.com:5432/iceberg |
Additional JDBC driver JARs must be provided via the -Djdbc.extra.driver.jars
JVM flag. Provide a comma-separated list of absolute paths:
-Djdbc.extra.driver.jars=/opt/drivers/postgresql.jar,/opt/drivers/mysql.jar
AWS Glue
Amazon Web Services Glue Data Catalog integration.
| Property | Required | Description |
|---|---|---|
uri | Yes | AWS Glue endpoint URL |
s3.access-key-id | Yes | AWS access key ID |
s3.secret-access-key | Yes | AWS secret access key |
aws.region | Yes | AWS region, e.g. us-east-1 |
Authentication uses AWS IAM credentials. Kerberos is not applicable.
REST
Catalogs accessible via the Apache Iceberg REST Catalog API.
| Property | Required | Description |
|---|---|---|
uri | Yes | REST catalog endpoint, e.g. http://rest-catalog.example.com:8234/catalog |
s3.endpoint | No | S3-compatible storage endpoint (for non-AWS storage) |
rest.sigv4-enabled | No | Set to true to enable AWS SigV4 request signing |
rest.authorization.header.enabled | No | Set to true to include authorization headers |
Nessie
Project Nessie versioned catalog with git-like branching for Iceberg tables.
| Property | Required | Description |
|---|---|---|
uri | Yes | Nessie API endpoint, e.g. http://nessie.example.com:19120/api/v1 |
ref | No | Branch or tag reference (default: main) |
warehouse | No | Default warehouse location, e.g. s3://bucket/path |
Adding Custom Properties
All catalog types accept additional properties via the Add property button on the catalog creation or settings page. These are passed directly to the underlying Iceberg catalog implementation.
Common additional properties include:
| Property | Description |
|---|---|
io-impl | Custom FileIO implementation class |
s3.endpoint | S3-compatible storage endpoint |
s3.path-style-access | Use path-style S3 URLs (true/false) |
s3.region | Override S3 region |
client.assume-role.arn | AWS IAM role ARN to assume |
Catalog properties also flow through to the FileIO used during data transfers, so a region or credentials set on the catalog apply to the target bucket too. Properties on a matched warehouse override the catalog values, letting you target a different region or set of credentials per warehouse.