Yandex Cloud
Search
Discuss with expertTry it for free
  • Customer Stories
  • Documentation
  • Blog
  • All Services
    • Cloud Interconnect
    • Cloud Backup
    • Cloud Registry
    • Yandex AI Studio
    • Compute Cloud
    • Object Storage
    • Managed Service for Kubernetes®
    • Yandex BareMetal
    • Smart Web Security
    • Security Deck
    • Managed Service for PostgreSQL
    • Managed Service for ClickHouse®
    • Monium
    • Cloud CDN
    • Network Load Balancer
    • Virtual Private Cloud
    • Cloud DNS
    • Application Load Balancer
    • Yandex Cloud Video
    • Stackland
    • Yandex Cloud Router
    • Yandex Managed Service for Trino
    • Managed Service for MySQL®
    • Managed Service for Valkey™
    • Managed Service for Apache Spark™
    • Yandex StoreDoc
    • Managed Service for OpenSearch
    • Managed Service for Apache Kafka®
    • Data Transfer
    • Yandex MPP Analytics Engine for PostgreSQL
    • Yandex Managed Service for Apache Airflow®
    • Data Processing
    • Yandex MetaData Hub
    • Managed Service for YDB
    • Managed Service for Sharded PostgreSQL
    • Managed Service for YTsaurus
    • Yandex WebSQL
    • DataLens
    • Yandex Search API
    • SpeechSense
    • SpeechKit
    • DataSphere
    • Vision OCR
    • Translate
    • Yandex Identity Hub
    • Key Management Service
    • Certificate Manager
    • Yandex Lockbox
    • Audit Trails
    • SmartCaptcha
    • Cloud Desktop
    • SourceCraft Code Assistant
    • Container Registry
    • Managed Service for GitLab
    • Managed Service for Prometheus®
    • Cloud Functions
    • API Gateway
    • Yandex Cloud Postbox
    • Message Queue
    • Serverless Integrations
    • IoT Core
    • Data Streams
    • Serverless Containers
    • Cloud Notification Service
    • Yandex Query
    • Identity and Access Management
    • Yandex Cloud Console
    • Resource Manager
    • Yandex Cloud Billing
    • Yandex Cloud Quota Manager
    • Cloud Apps
  • System Status
  • Marketplace
    • Featured
    • Infrastructure & Network
    • Data Platform
    • AI for business
    • Security
    • DevOps tools
    • Serverless
    • Monitoring & Resources
  • All Solutions
    • By industry
    • By use case
    • Economics and Pricing
    • Security
    • Technical Support
    • Start testing with double trial credits
    • Cloud credits to scale your IT product
    • Gateway to Russia
    • Cloud for Startups
    • Center for Technologies and Society
    • Yandex Cloud Partner program
    • Price calculator
    • Pricing plans
  • Customer Stories
  • Documentation
  • Blog
© 2026 Direct Cursus Technology L.L.C.
Yandex Cloud Stackland
  • What's new
  • Installation
    • All tutorials
    • Installing Stackland on Yandex BareMetal
    • Installing Stackland on Yandex BareMetal via PXE
    • Installing Stackland on Yandex Cloud VMs
    • Setting up external access to a pod in a cluster
    • All guides
        • Creating a Trino cluster
        • Updating cluster settings
        • Deleting a cluster
        • Creating a catalog
        • Updating catalog settings
        • Deleting a folder.
    • Projects
    • Resource model
    • Scaling a cluster
  • Access management
  • Pricing policy
  • Diagnostics and troubleshooting
  1. Step-by-step guides
  2. Databases
  3. Managed Service for Trino
  4. Updating catalog settings

Updating Managed Service for Trino catalog settings

Written by
Yandex Cloud
Updated at July 24, 2026
View in Markdown

If you have a catalog in your Trino cluster, you can update the catalog’s settings.

Note

When you update a catalog, Managed Service for Trino recreates the cluster. While the new configuration is being applied, the cluster switches to Updating, and active queries get interrupted. For more information, see Updating a cluster.

CLI
Management console
  1. Open the TrinoCatalog resource file, e.g., using the open trinocatalog.yaml command.

  2. Edit the properties of the selected catalog type.

    General properties:

    • spec.<type>.url: Data source address
    • spec.<type>.additionalProperties: Advanced connector settings.

    For PostgreSQL and ClickHouse catalogs, the following properties are also available:

    • spec.<type>.credentialsSecretRef: Reference to the Secret with credentials.
    • spec.<type>.certificateSecretRef: Reference to the Secret with a TLS certificate.

    The spec.cluster, spec.name, and spec.type fields are immutable: spec.cluster and spec.name make up the resource name (metadata.name), and modifying spec.type is not supported.

    For Iceberg catalogs, the following properties are also available:

    • spec.iceberg.rest.warehouse: REST catalog name.
    • spec.iceberg.rest.oauth2: Authentication parameters (static token or client credentials).
    • spec.iceberg.s3: S3 storage settings.
    • spec.iceberg.stacklandStorage.bucketRef: Link to an Object Storage bucket.
  3. Apply the manifest: kubectl apply -f trinocatalog.yaml -n <namespace>.

If you store credentials in a Secret, update the Secret independently. You do not need to rename the secret name or keys.

  1. If you have not opened a project yet, select one.

  2. Select the namespace the cluster was created in.

  3. In the left-hand menu, select Trino → Clusters.

  4. Select the cluster and open the Catalogs tab.

  5. Select the catalog.

  6. Click Edit.

  7. Edit the catalog configuration under Catalog settings. The Name and Type fields are read-only.

    The Secret fields, such as Password, Access token, Client secret, and Secret access key, are empty. If you save them as is, the existing Secret values will remain unchanged. Enter a new value to update the secret.

    In the Additional settings section, the key is read-only for existing rows; you can only change the value. Still, you can add new keys.

  8. Click Save.

Done. The catalog settings have been updated.

Was the article helpful?

Previous
Creating a catalog
Next
Deleting a folder.
© 2026 Direct Cursus Technology L.L.C.