yandex_trino_catalog (Resource)

Catalog for Manage Trino cluster.

Example usageExample usage

//
// Create a new Trino catalog
//

resource "yandex_trino_catalog" "catalog" {
  name        = "name"
  description = "descriptionr"
  cluster_id  = yandex_trino_cluster.trino.id
  postgresql = {
    connection_manager = {
      connection_id = "<connection_id>"
      database      = "database-name"
      connection_properties = {
        "targetServerType" = "primary"
      }
    }
  }
}

SchemaSchema

RequiredRequired

• cluster_id (String) ID of the Trino cluster. Provided by the client when the Catalog is created.
• name (String) The resource name.

OptionalOptional

• clickhouse (Attributes) Configuration for Clickhouse connector. (see below for nested schema)
• delta_lake (Attributes) Configuration for DeltaLake connector. (see below for nested schema)
• description (String) The resource description.
• hive (Attributes) Configuration for Hive connector. (see below for nested schema)
• hudi (Attributes) Configuration for Hudi connector. (see below for nested schema)
• iceberg (Attributes) Configuration for Iceberg connector. (see below for nested schema)
• labels (Map of String) A set of key/value label pairs which assigned to resource.
• oracle (Attributes) Configuration for Oracle connector. (see below for nested schema)
• postgresql (Attributes) Configuration for Postgresql connector. (see below for nested schema)
• sqlserver (Attributes) Configuration for SQLServer connector. (see below for nested schema)
• timeouts (Block, Optional) (see below for nested schema)
• tpcds (Attributes) Configuration for TPCDS connector. (see below for nested schema)
• tpch (Attributes) Configuration for TPCH connector. (see below for nested schema)

Read-OnlyRead-Only

• id (String) The resource identifier.

Nested Schema for Nested Schema for clickhouse

Optional:

• additional_properties (Map of String) Additional properties.
• connection_manager (Attributes) Configuration for connection manager connection. (see below for nested schema)
• on_premise (Attributes) Configuration for on-premise connection. (see below for nested schema)

Nested Schema for Nested Schema for clickhouse.connection_manager

Required:

• connection_id (String) Connection ID.
• database (String) Database.

Optional:

• connection_properties (Map of String) Additional connection properties.

Nested Schema for Nested Schema for clickhouse.on_premise

Required:

• connection_url (String) Connection to the clickhouse.
• password (String) Password of the clickhouse user.
• user_name (String) Name of the clickhouse user.

Nested Schema for Nested Schema for delta_lake

Required:

• file_system (Attributes) File system configuration. (see below for nested schema)
• metastore (Attributes) Metastore configuration. (see below for nested schema)

Optional:

• additional_properties (Map of String) Additional properties.

Nested Schema for Nested Schema for delta_lake.file_system

Optional:

• external_s3 (Attributes) Describes External S3 compatible file system. (see below for nested schema)
• s3 (Attributes) Describes YandexCloud native S3 file system. (see below for nested schema)

Nested Schema for Nested Schema for delta_lake.file_system.external_s3

Required:

• aws_access_key (String, Sensitive) AWS access key ID for S3 authentication.
• aws_endpoint (String) AWS S3 compatible endpoint URL.
• aws_region (String) AWS region for S3 storage.
• aws_secret_key (String, Sensitive) AWS secret access key for S3 authentication.

Nested Schema for Nested Schema for delta_lake.file_system.s3

Nested Schema for Nested Schema for delta_lake.metastore

Required:

• uri (String) The resource description.

Nested Schema for Nested Schema for hive

Required:

• file_system (Attributes) File system configuration. (see below for nested schema)
• metastore (Attributes) Metastore configuration. (see below for nested schema)

Optional:

• additional_properties (Map of String) Additional properties.

Nested Schema for Nested Schema for hive.file_system

Optional:

• external_s3 (Attributes) Describes External S3 compatible file system. (see below for nested schema)
• s3 (Attributes) Describes YandexCloud native S3 file system. (see below for nested schema)

Nested Schema for Nested Schema for hive.file_system.external_s3

Required:

• aws_access_key (String, Sensitive) AWS access key ID for S3 authentication.
• aws_endpoint (String) AWS S3 compatible endpoint URL.
• aws_region (String) AWS region for S3 storage.
• aws_secret_key (String, Sensitive) AWS secret access key for S3 authentication.

Nested Schema for Nested Schema for hive.file_system.s3

Nested Schema for Nested Schema for hive.metastore

Required:

• uri (String) The resource description.

Nested Schema for Nested Schema for hudi

Required:

• file_system (Attributes) File system configuration. (see below for nested schema)
• metastore (Attributes) Metastore configuration. (see below for nested schema)

Optional:

• additional_properties (Map of String) Additional properties.

Nested Schema for Nested Schema for hudi.file_system

Optional:

• external_s3 (Attributes) Describes External S3 compatible file system. (see below for nested schema)
• s3 (Attributes) Describes YandexCloud native S3 file system. (see below for nested schema)

Nested Schema for Nested Schema for hudi.file_system.external_s3

Required:

• aws_access_key (String, Sensitive) AWS access key ID for S3 authentication.
• aws_endpoint (String) AWS S3 compatible endpoint URL.
• aws_region (String) AWS region for S3 storage.
• aws_secret_key (String, Sensitive) AWS secret access key for S3 authentication.

Nested Schema for Nested Schema for hudi.file_system.s3

Nested Schema for Nested Schema for hudi.metastore

Required:

• uri (String) The resource description.

Nested Schema for Nested Schema for iceberg

Required:

• file_system (Attributes) File system configuration. (see below for nested schema)
• metastore (Attributes) Metastore configuration. (see below for nested schema)

Optional:

• additional_properties (Map of String) Additional properties.

Nested Schema for Nested Schema for iceberg.file_system

Optional:

• external_s3 (Attributes) Describes External S3 compatible file system. (see below for nested schema)
• s3 (Attributes) Describes YandexCloud native S3 file system. (see below for nested schema)

Nested Schema for Nested Schema for iceberg.file_system.external_s3

Required:

• aws_access_key (String, Sensitive) AWS access key ID for S3 authentication.
• aws_endpoint (String) AWS S3 compatible endpoint URL.
• aws_region (String) AWS region for S3 storage.
• aws_secret_key (String, Sensitive) AWS secret access key for S3 authentication.

Nested Schema for Nested Schema for iceberg.file_system.s3

Nested Schema for Nested Schema for iceberg.metastore

Required:

• uri (String) The resource description.

Nested Schema for Nested Schema for oracle

Optional:

• additional_properties (Map of String) Additional properties.
• on_premise (Attributes) Configuration for on-premise connection. (see below for nested schema)

Nested Schema for Nested Schema for oracle.on_premise

Required:

• connection_url (String) Connection to the clickhouse.
• password (String) Password of the clickhouse user.
• user_name (String) Name of the clickhouse user.

Nested Schema for Nested Schema for postgresql

Optional:

• additional_properties (Map of String) Additional properties.
• connection_manager (Attributes) Configuration for connection manager connection. (see below for nested schema)
• on_premise (Attributes) Configuration for on-premise connection. (see below for nested schema)

Nested Schema for Nested Schema for postgresql.connection_manager

Required:

• connection_id (String) Connection ID.
• database (String) Database.

Optional:

• connection_properties (Map of String) Additional connection properties.

Nested Schema for Nested Schema for postgresql.on_premise

Required:

• connection_url (String) Connection to the clickhouse.
• password (String) Password of the clickhouse user.
• user_name (String) Name of the clickhouse user.

Nested Schema for Nested Schema for sqlserver

Optional:

• additional_properties (Map of String) Additional properties.
• on_premise (Attributes) Configuration for on-premise connection. (see below for nested schema)

Nested Schema for Nested Schema for sqlserver.on_premise

Required:

• connection_url (String) Connection to the clickhouse.
• password (String) Password of the clickhouse user.
• user_name (String) Name of the clickhouse user.

Nested Schema for Nested Schema for timeouts

Optional:

• create (String) A string that can be parsed as a duration consisting of numbers and unit suffixes, such as "30s" or "2h45m". Valid time units are "s" (seconds), "m" (minutes), "h" (hours). A string that can be parsed as a duration consisting of numbers and unit suffixes, such as "30s" or "2h45m". Valid time units are "s" (seconds), "m" (minutes), "h" (hours).
• delete (String) A string that can be parsed as a duration consisting of numbers and unit suffixes, such as "30s" or "2h45m". Valid time units are "s" (seconds), "m" (minutes), "h" (hours). Setting a timeout for a Delete operation is only applicable if changes are saved into state before the destroy operation occurs.
• update (String) A string that can be parsed as a duration consisting of numbers and unit suffixes, such as "30s" or "2h45m". Valid time units are "s" (seconds), "m" (minutes), "h" (hours).

Nested Schema for Nested Schema for tpcds

Optional:

• additional_properties (Map of String) Additional properties.

Nested Schema for Nested Schema for tpch

Optional:

• additional_properties (Map of String) Additional properties.

ImportImport

The resource can be imported by using their resource ID. For getting the resource ID you can use Yandex Cloud Web Console or YC CLI.

# terraform import yandex_trino_catalog.<resource Name> <cluster_id>:<resource_id>
terraform import yandex_trino_catalog.my_catalog cluster_id:catalog_id