Yandex Cloud
Поиск
Связаться с намиПодключиться
  • Истории успеха
  • Документация
  • Блог
  • Все сервисы
  • Статус работы сервисов
    • Доступны в регионе
    • Инфраструктура и сеть
    • Платформа данных
    • Контейнеры
    • Инструменты разработчика
    • Бессерверные вычисления
    • Безопасность
    • Мониторинг и управление ресурсами
    • ИИ для бизнеса
    • Бизнес-инструменты
  • Все решения
    • По отраслям
    • По типу задач
    • Экономика платформы
    • Безопасность
    • Техническая поддержка
    • Каталог партнёров
    • Обучение и сертификация
    • Облако для стартапов
    • Облако для крупного бизнеса
    • Центр технологий для общества
    • Партнёрская программа
    • Поддержка IT-бизнеса
    • Облако для фрилансеров
    • Обучение и сертификация
    • Блог
    • Документация
    • Мероприятия и вебинары
    • Контакты, чаты и сообщества
    • Идеи
    • Тарифы Yandex Cloud
    • Промоакции и free tier
    • Правила тарификации
  • Истории успеха
  • Документация
  • Блог
Проект Яндекса
© 2025 ТОО «Облачные Сервисы Казахстан»
Terraform в Yandex Cloud
  • Начало работы
  • Библиотека решений
    • Обзор
    • История изменений (англ.)
          • metastore_cluster

В этой статье:

  • Example usage
  • Schema
  • Optional
  • Read-Only
  • Nested Schema for timeouts
  • Nested Schema for cluster_config
  • Nested Schema for logging
  • Nested Schema for maintenance_window
  1. Справочник Terraform
  2. Ресурсы (англ.)
  3. Apache Hive Metastore
  4. Data Sources
  5. metastore_cluster

yandex_metastore_cluster (Data Source)

Статья создана
Yandex Cloud
Обновлена 13 ноября 2025 г.
  • Example usage
  • Schema
    • Optional
    • Read-Only
    • Nested Schema for timeouts
    • Nested Schema for cluster_config
    • Nested Schema for logging
    • Nested Schema for maintenance_window

Managed Metastore cluster.

Example usageExample usage

//
// Get information about Metastore Cluster by name
//
data "yandex_metastore_cluster" "metastore_cluster_by_name" {
  name = "metastore-created-with-terraform"
}

//
// Get information about Metastore Cluster by id
//
data "yandex_metastore_cluster" "metastore_cluster_by_id" {
  id = "<metastore-cluster-id>"
}

SchemaSchema

OptionalOptional

  • id (String) The resource identifier.
  • name (String) The resource name.
  • timeouts (Block, Optional) (see below for nested schema)
  • version (String) Metastore server version.

Read-OnlyRead-Only

  • cluster_config (Attributes) Hive Metastore cluster configuration. (see below for nested schema)
  • created_at (String) The creation timestamp of the resource.
  • deletion_protection (Boolean) The true value means that resource is protected from accidental deletion. By default is set to false.
  • description (String) The resource description.
  • endpoint_ip (String) IP address of Metastore server balancer endpoint.
  • folder_id (String) The folder identifier that resource belongs to. If it is not provided, the default provider folder-id is used.
  • labels (Map of String) A set of key/value label pairs which assigned to resource.
  • logging (Attributes) Cloud Logging configuration. (see below for nested schema)
  • maintenance_window (Attributes) Configuration of window for maintenance operations. (see below for nested schema)
  • network_id (String) VPC network identifier which resource is attached.
  • security_group_ids (Set of String) The list of security groups applied to resource or their components.
  • service_account_id (String) Service account with role managed-metastore.integrationProvider. For more information, see documentation.
  • status (String) Status of the cluster. Can be either CREATING, STARTING, RUNNING, UPDATING, STOPPING, STOPPED, ERROR or STATUS_UNKNOWN.
  • subnet_ids (Set of String) The list of VPC subnets identifiers which resource is attached.

Nested Schema for Nested Schema for timeouts

Optional:

  • read (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). Read operations occur during any refresh or planning operation when refresh is enabled.

Nested Schema for Nested Schema for cluster_config

Read-Only:

  • resource_preset_id (String) The identifier of the preset for computational resources available to an instance (CPU, memory etc.).

Nested Schema for Nested Schema for logging

Read-Only:

  • enabled (Boolean) Enables delivery of logs generated by Metastore to Cloud Logging.
  • folder_id (String) Logs will be written to default log group of specified folder. Exactly one of the attributes folder_id or log_group_id should be specified.
  • log_group_id (String) Logs will be written to the specified log group. Exactly one of the attributes folder_id or log_group_id should be specified.
  • min_level (String) Minimum level of messages that will be sent to Cloud Logging. Can be either TRACE, DEBUG, INFO, WARN, ERROR or FATAL. If not set then server default is applied (currently INFO).

Nested Schema for Nested Schema for maintenance_window

Read-Only:

  • day (String) Day of week for maintenance window. One of MON, TUE, WED, THU, FRI, SAT, SUN.
  • hour (Number) Hour of day in UTC time zone (1-24) for maintenance window.
  • type (String) Type of maintenance window. Can be either ANYTIME or WEEKLY. If WEEKLY, day and hour must be specified.

Была ли статья полезна?

Предыдущая
История изменений (англ.)
Следующая
metastore_cluster
Проект Яндекса
© 2025 ТОО «Облачные Сервисы Казахстан»