Catalog NVPs | Teradata Vantage - Catalog Name-Value Pairs - Teradata Vantage

Teradata® Open Table Format for Apache Iceberg and Delta Lake User Guide
Deployment
VantageCloud
VantageCore
Edition
VMware
Enterprise
IntelliFlex
Lake
Product
Teradata Vantage
Release Number
20.00
Published
October 2025
ft:locale
en-US
ft:lastEdition
2026-06-17
dita:mapPath
qrj1749167830193.ditamap
dita:ditavalPath
lli1749584660955.ditaval
dita:id
bsr1702324250454

The catalog name-value pair (NVP) specification includes the following parameters that OTF uses to perform catalog operations:

NVP Name Description
catalog_type Specifies the Iceberg catalog type. Allowed value: rest.
rest_catalog_type

Specifies the REST Iceberg catalog type. This name–value pair is newly introduced to support stronger validation in OTF and to automatically provide default values for certain parameters when applicable to the supported REST catalogs:

Allowed values:

  • default: Placeholder for future catalog types.
  • polaris: Use for Polaris catalog.
  • gravitino: Use for Gravitino catalog.

    unity: Use for Unity catalog.

  • biglake: Use for BigLake catalog.
If this name-value pair is not specified during datalake creation, OTF automatically assigns the value "default".

Default values for other name-value pairs are automatically applied based on the selected rest_catalog_type. This reduces the need for users to specify these parameters when the defaults meet their requirements. .
catalog_location URL endpoint for the Iceberg catalog REST API
catalog_name Name/identifier of the catalog.
catalog_headers REST header information must be provided as a JSON string.

This name-value pair is newly introduced to support the Polaris realm concept in OTF. OTF uses this setting to pass realm details as name-value pairs, ensuring they align with the configuration defined in the Polaris service.