Updating a Trino cluster

If you do not have the Yandex Cloud CLI installed yet, install and initialize it.

By default, the CLI uses the folder specified when creating the profile. To change the default folder, use the yc config set folder-id <folder_ID> command. You can also set a different folder for any specific command using the --folder-name or --folder-id parameter.

To change cluster name and description:

1. View the description of the CLI command for updating a cluster:

   yc managed-trino cluster update --help
   

2. To change cluster name and description, run this command:

   yc managed-trino cluster update <cluster_name_or_ID> \
     --new-name <cluster_name> \
     --description <cluster_description> 
   

   Where:

   • --new-name: Cluster name, unique within the cloud.
   • --description: Cluster description.

   You can get the cluster name and ID with the list of clusters in the folder.

1. Open the current Terraform configuration file describing your infrastructure.

   For more information about creating this file, see this guide.

2. Edit the description parameter in the cluster's description:

   resource "yandex_trino_cluster" "<cluster_name>" {
     ...
     description = "<cluster_description>"
     ...
   }
   

   Where description is the cluster's description.

3. Validate your configuration.

   1. In the command line, navigate to the directory that contains the current Terraform configuration files defining the infrastructure.

   2. Run this command:

      terraform validate
      

      Terraform will show any errors found in your configuration files.

4. Confirm resource changes.

   1. Run this command to view the planned changes:

      terraform plan
      

      If you described the configuration correctly, the terminal will display a list of the resources to update and their parameters. This is a verification step that does not apply changes to your resources.

   2. If everything looks correct, apply the changes:

      1. Run this command:

         terraform apply
         

      2. Confirm updating the resources.

      3. Wait for the operation to complete.

1. Get an IAM token for API authentication and place it in an environment variable:

   export IAM_TOKEN="<IAM_token>"
   

2. Create a file named body.json and paste the following code into it:

   {
     "updateMask": "<list_of_parameters_to_update>",
     "name": "<cluster_name>",
     "description": "<cluster_description>"
   }
   

   Where:

   • updateMask: Comma-separated list of parameters to update.

     Warning

     When you update a cluster, all parameters of the object you are modifying will take their defaults unless explicitly provided in the request. To avoid this, list the settings you want to change in the updateMask parameter.

   • name: Cluster name, unique within the cloud.

   • description: Cluster description.

3. Use the Cluster.Update method and send the following request, e.g., via cURL:

   curl \
     --request PATCH \
     --header "Authorization: Bearer $IAM_TOKEN" \
     --url 'https://trino.api.cloud.yandex.net/managed-trino/v1/clusters/<cluster_ID>'
     --data '@body.json'
   

   You can get the cluster ID with the list of clusters in the folder.

4. Check the server response to make sure your request was successful.

1. Get an IAM token for API authentication and place it in an environment variable:

   export IAM_TOKEN="<IAM_token>"
   

2. Clone the cloudapi repository:

   cd ~/ && git clone --depth=1 https://github.com/yandex-cloud/cloudapi
   

   Below, we assume the repository contents are stored in the ~/cloudapi/ directory.

3. Create a file named body.json and paste the following code into it:

   {
     "cluster_id": "<cluster_ID>",
     "update_mask": {
       "paths": [
         <list_of_parameters_to_update>
       ]
     },
     "name": "<cluster_name>",
     "description": "<cluster_description>"
   }
   

   Where:

   • cluster_id: Cluster ID.

     You can get the cluster ID with the list of clusters in the folder.

   • update_mask: List of settings you want to modify as an array of strings (paths[]).

     Format for listing settings

     "update_mask": {
       "paths": [
         "<setting_1>",
         "<setting_2>",
         ...
         "<setting_N>"
       ]
     }
     

     Warning

     When you update a cluster, all parameters of the object you are modifying will take their defaults unless explicitly provided in the request. To avoid this, list the settings you want to change in the update_mask parameter.

   • name: Cluster name, unique within the cloud.

   • description: Cluster description.

4. Use the ClusterService.Update call and send the following request, e.g., via gRPCurl:

   grpcurl \
     -format json \
     -import-path ~/cloudapi/ \
     -import-path ~/cloudapi/third_party/googleapis/ \
     -proto ~/cloudapi/yandex/cloud/trino/v1/cluster_service.proto \
     -rpc-header "Authorization: Bearer $IAM_TOKEN" \
     -d @ \
     trino.api.cloud.yandex.net:443 \
     yandex.cloud.trino.v1.ClusterService.Update \
     < body.json
   

5. Check the server response to make sure your request was successful.

If you do not have the Yandex Cloud CLI installed yet, install and initialize it.

By default, the CLI uses the folder specified when creating the profile. To change the default folder, use the yc config set folder-id <folder_ID> command. You can also set a different folder for any specific command using the --folder-name or --folder-id parameter.

To update a service account:

1. View the description of the CLI command for updating a cluster:

   yc managed-trino cluster update --help
   

2. Update your service account using this command:

   yc managed-trino cluster update <cluster_name_or_ID> \
     --service-account-id <service_account_ID>
   

   Where --service-account-id is the service account ID.

   You can get the cluster name and ID with the list of clusters in the folder.

1. Open the current Terraform configuration file describing your infrastructure.

   For more information about creating this file, see this guide.

2. Edit the service_account_id parameter in the cluster's description:

   resource "yandex_trino_cluster" "<cluster_name>" {
     ...
     service_account_id  = "<service_account_ID>"
     ...
   }
   

   Where service_account_id is the service account ID.

3. Validate your configuration.

   1. In the command line, navigate to the directory that contains the current Terraform configuration files defining the infrastructure.

   2. Run this command:

      terraform validate
      

      Terraform will show any errors found in your configuration files.

4. Confirm resource changes.

   1. Run this command to view the planned changes:

      terraform plan
      

      If you described the configuration correctly, the terminal will display a list of the resources to update and their parameters. This is a verification step that does not apply changes to your resources.

   2. If everything looks correct, apply the changes:

      1. Run this command:

         terraform apply
         

      2. Confirm updating the resources.

      3. Wait for the operation to complete.

1. Get an IAM token for API authentication and place it in an environment variable:

   export IAM_TOKEN="<IAM_token>"
   

2. Create a file named body.json and paste the following code into it:

   {
     "updateMask": "serviceAccountId",
     "serviceAccountId": "<service_account_ID>"
   }
   

   Where:

   • updateMask: Comma-separated list of parameters to update.

     Warning

     When you update a cluster, all parameters of the object you are modifying will take their defaults unless explicitly provided in the request. To avoid this, list the settings you want to change in the updateMask parameter.

   • serviceAccountId: Service account ID.

3. Use the Cluster.Update method and send the following request, e.g., via cURL:

   curl \
       --request PATCH \
       --header "Authorization: Bearer $IAM_TOKEN" \
       --url 'https://trino.api.cloud.yandex.net/managed-trino/v1/clusters/<cluster_ID>'
       --data '@body.json'
   

   You can get the cluster ID with the list of clusters in the folder.

4. Check the server response to make sure your request was successful.

1. Get an IAM token for API authentication and place it in an environment variable:

   export IAM_TOKEN="<IAM_token>"
   

2. Clone the cloudapi repository:

   cd ~/ && git clone --depth=1 https://github.com/yandex-cloud/cloudapi
   

   Below, we assume the repository contents are stored in the ~/cloudapi/ directory.

3. Create a file named body.json and paste the following code into it:

   {
     "cluster_id": "<cluster_ID>",
     "update_mask": {
       "paths": [
         "service_account_id"
       ]
     },
     "service_account_id": "<service_account_ID>"
   }
   

   Where:

   • cluster_id: Cluster ID.

     You can get the cluster ID with the list of clusters in the folder.

   • update_mask: List of settings you want to modify as an array of strings (paths[]).

     Format for listing settings

     "update_mask": {
       "paths": [
         "<setting_1>",
         "<setting_2>",
         ...
         "<setting_N>"
       ]
     }
     

     Warning

     When you update a cluster, all parameters of the object you are modifying will take their defaults unless explicitly provided in the request. To avoid this, list the settings you want to change in the update_mask parameter.

   • service_account_id: Service account ID.

4. Use the ClusterService.Update call and send the following request, e.g., via gRPCurl:

   grpcurl \
     -format json \
     -import-path ~/cloudapi/ \
     -import-path ~/cloudapi/third_party/googleapis/ \
     -proto ~/cloudapi/yandex/cloud/trino/v1/cluster_service.proto \
     -rpc-header "Authorization: Bearer $IAM_TOKEN" \
     -d @ \
     trino.api.cloud.yandex.net:443 \
     yandex.cloud.trino.v1.ClusterService.Update \
     < body.json
   

5. Check the server response to make sure your request was successful.

If you do not have the Yandex Cloud CLI installed yet, install and initialize it.

By default, the CLI uses the folder specified when creating the profile. To change the default folder, use the yc config set folder-id <folder_ID> command. You can also set a different folder for any specific command using the --folder-name or --folder-id parameter.

To change the Trino version:

1. View the description of the CLI command for updating a cluster:

   yc managed-trino cluster update --help
   

2. Change the version by running this command:

   yc managed-trino cluster update <cluster_name_or_ID> \
     --version <version>
   

   Where --version is the Trino version. You can either upgrade or downgrade the version.

   You can get the cluster name and ID with the list of clusters in the folder.

1. Open the current Terraform configuration file describing your infrastructure.

   For more information about creating this file, see this guide.

2. Edit the version parameter in the cluster's description:

   resource "yandex_trino_cluster" "<cluster_name>" {
     ...
     version = "<version>"
     ...
   }
   

   Where version is the Trino version. You can either upgrade or downgrade the version.

3. Validate your configuration.

   1. In the command line, navigate to the directory that contains the current Terraform configuration files defining the infrastructure.

   2. Run this command:

      terraform validate
      

      Terraform will show any errors found in your configuration files.

4. Confirm resource changes.

   1. Run this command to view the planned changes:

      terraform plan
      

      If you described the configuration correctly, the terminal will display a list of the resources to update and their parameters. This is a verification step that does not apply changes to your resources.

   2. If everything looks correct, apply the changes:

      1. Run this command:

         terraform apply
         

      2. Confirm updating the resources.

      3. Wait for the operation to complete.

1. Get an IAM token for API authentication and place it in an environment variable:

   export IAM_TOKEN="<IAM_token>"
   

2. Create a file named body.json and paste the following code into it:

   {
     "updateMask": "trino.version",
     "trino": {
       "version": "<version>"
     }
   }
   

   Where:

   • updateMask: Comma-separated list of parameters to update.

     Warning

     When you update a cluster, all parameters of the object you are modifying will take their defaults unless explicitly provided in the request. To avoid this, list the settings you want to change in the updateMask parameter.

   • version: Trino version. You can either upgrade or downgrade the version.

3. Use the Cluster.Update method and send the following request, e.g., via cURL:

   curl \
     --request PATCH \
     --header "Authorization: Bearer $IAM_TOKEN" \
     --url 'https://trino.api.cloud.yandex.net/managed-trino/v1/clusters/<cluster_ID>'
     --data '@body.json'
   

   You can get the cluster ID with the list of clusters in the folder.

4. Check the server response to make sure your request was successful.

1. Get an IAM token for API authentication and place it in an environment variable:

   export IAM_TOKEN="<IAM_token>"
   

2. Clone the cloudapi repository:

   cd ~/ && git clone --depth=1 https://github.com/yandex-cloud/cloudapi
   

   Below, we assume the repository contents are stored in the ~/cloudapi/ directory.

3. Create a file named body.json and paste the following code into it:

   {
     "cluster_id": "<cluster_ID>",
     "update_mask": {
       "paths": [
         "trino.version"
       ]
     },
     "trino": {
       "version": "<version>"
     }
   }
   

   Where:

   • cluster_id: Cluster ID.

     You can get the cluster ID with the list of clusters in the folder.

   • update_mask: List of settings you want to modify as an array of strings (paths[]).

     Format for listing settings

     "update_mask": {
       "paths": [
         "<setting_1>",
         "<setting_2>",
         ...
         "<setting_N>"
       ]
     }
     

     Warning

     When you update a cluster, all parameters of the object you are modifying will take their defaults unless explicitly provided in the request. To avoid this, list the settings you want to change in the update_mask parameter.

   • version: Trino version. You can either upgrade or downgrade the version.

4. Use the ClusterService.Update call and send the following request, e.g., via gRPCurl:

   grpcurl \
     -format json \
     -import-path ~/cloudapi/ \
     -import-path ~/cloudapi/third_party/googleapis/ \
     -proto ~/cloudapi/yandex/cloud/trino/v1/cluster_service.proto \
     -rpc-header "Authorization: Bearer $IAM_TOKEN" \
     -d @ \
     trino.api.cloud.yandex.net:443 \
     yandex.cloud.trino.v1.ClusterService.Update \
     < body.json
   

5. Check the server response to make sure your request was successful.

If you do not have the Yandex Cloud CLI installed yet, install and initialize it.

By default, the CLI uses the folder specified when creating the profile. To change the default folder, use the yc config set folder-id <folder_ID> command. You can also set a different folder for any specific command using the --folder-name or --folder-id parameter.

To update security groups:

1. View the description of the CLI command for updating a cluster:

   yc managed-trino cluster update --help
   

2. Update security groups using this command:

   yc managed-trino cluster update <cluster_name_or_ID> \
     --security-group-ids <list_of_security_group_IDs>
   

   Where --security-group-ids is the list of security group IDs.

   You can get the cluster name and ID with the list of clusters in the folder.

1. Open the current Terraform configuration file describing your infrastructure.

   For more information about creating this file, see this guide.

2. Edit the security_group_ids parameter in the cluster's description:

   resource "yandex_trino_cluster" "<cluster_name>" {
     ...
     security_group_ids  = [<list_of_security_group_IDs>]
     ...
   }
   

   Where security_group_ids is the list of security group IDs.

3. Validate your configuration.

   1. In the command line, navigate to the directory that contains the current Terraform configuration files defining the infrastructure.

   2. Run this command:

      terraform validate
      

      Terraform will show any errors found in your configuration files.

4. Confirm resource changes.

   1. Run this command to view the planned changes:

      terraform plan
      

      If you described the configuration correctly, the terminal will display a list of the resources to update and their parameters. This is a verification step that does not apply changes to your resources.

   2. If everything looks correct, apply the changes:

      1. Run this command:

         terraform apply
         

      2. Confirm updating the resources.

      3. Wait for the operation to complete.

1. Get an IAM token for API authentication and place it in an environment variable:

   export IAM_TOKEN="<IAM_token>"
   

2. Create a file named body.json and paste the following code into it:

   {
     "updateMask": "networkSpec.securityGroupIds",
     "networkSpec": {
       "securityGroupIds": [
         <list_of_security_group_IDs>
       ]
     }
   }
   

   Where:

   • updateMask: Comma-separated list of parameters to update.

     Warning

     When you update a cluster, all parameters of the object you are modifying will take their defaults unless explicitly provided in the request. To avoid this, list the settings you want to change in the updateMask parameter.

   • networkSpec: Network settings:

     • securityGroupIds: List of security group IDs.

3. Use the Cluster.Update method and send the following request, e.g., via cURL:

   curl \
     --request PATCH \
     --header "Authorization: Bearer $IAM_TOKEN" \
     --url 'https://trino.api.cloud.yandex.net/managed-trino/v1/clusters/<cluster_ID>'
     --data '@body.json'
   

   You can get the cluster ID with the list of clusters in the folder.

4. Check the server response to make sure your request was successful.

1. Get an IAM token for API authentication and place it in an environment variable:

   export IAM_TOKEN="<IAM_token>"
   

2. Clone the cloudapi repository:

   cd ~/ && git clone --depth=1 https://github.com/yandex-cloud/cloudapi
   

   Below, we assume the repository contents are stored in the ~/cloudapi/ directory.

3. Create a file named body.json and paste the following code into it:

   {
     "cluster_id": "<cluster_ID>",
     "update_mask": {
       "paths": [
         "network_spec.security_group_ids"
       ]
     },
     "network_spec": {
       "security_group_ids": [ <list_of_security_group_IDs> ]
     }
   }
   

   Where:

   • cluster_id: Cluster ID.

     You can get the cluster ID with the list of clusters in the folder.

   • update_mask: List of settings you want to modify as an array of strings (paths[]).

     Format for listing settings

     "update_mask": {
       "paths": [
         "<setting_1>",
         "<setting_2>",
         ...
         "<setting_N>"
       ]
     }
     

     Warning

     When you update a cluster, all parameters of the object you are modifying will take their defaults unless explicitly provided in the request. To avoid this, list the settings you want to change in the update_mask parameter.

   • network_spec: Network settings:

     • security_group_ids: List of security group IDs.

4. Use the ClusterService.Update call and send the following request, e.g., via gRPCurl:

   grpcurl \
     -format json \
     -import-path ~/cloudapi/ \
     -import-path ~/cloudapi/third_party/googleapis/ \
     -proto ~/cloudapi/yandex/cloud/trino/v1/cluster_service.proto \
     -rpc-header "Authorization: Bearer $IAM_TOKEN" \
     -d @ \
     trino.api.cloud.yandex.net:443 \
     yandex.cloud.trino.v1.ClusterService.Update \
     < body.json
   

5. Check the server response to make sure your request was successful.

If you do not have the Yandex Cloud CLI installed yet, install and initialize it.

By default, the CLI uses the folder specified when creating the profile. To change the default folder, use the yc config set folder-id <folder_ID> command. You can also set a different folder for any specific command using the --folder-name or --folder-id parameter.

To update fault-tolerant query execution parameters:

1. View the description of the CLI command for updating a cluster:

   yc managed-trino cluster update --help
   

2. Update the fault-tolerant query execution parameters using this command:

   yc managed-trino cluster update <cluster_name_or_ID> \
     --retry-policy-enabled \ 
     --retry-policy <object_type_for_retry> \
     --retry-policy-additional-properties <list_of_additional_parameters> \
     --retry-policy-exchange-manager-service-s3 \
     --retry-policy-exchange-manager-additional-properties <list_of_additional_parameters>
   

   Where:

   • --retry-policy-enabled: Enables the retry policy.

   • --retry-policy: Query retry method. The allowed values are:

     • query: Retries all stages of the query in which the worker failed.
     • task: Retries the intermediate task within the query that caused worker failure.

   • --retry-policy-additional-properties: Additional query retry parameters in <key>=<value> format. Learn more about parameters in the Trino documentation.

   • --retry-policy-exchange-manager-service-s3: Activates the use of a service Object Storage bucket as an Exchange Manager storage for intermediate data.

   • --retry-policy-exchange-manager-additional-properties: Additional Exchange Manager storage parameters in <key>=<value> format. Learn more about parameters in the Trino documentation.

   You can get the cluster name and ID with the list of clusters in the folder.

1. Open the current Terraform configuration file describing your infrastructure.

   For more information about creating this file, see this guide.

2. To enable a fault-tolerant query execution policy, add a retry_policy section to the cluster description:

   resource "yandex_trino_cluster" "<cluster_name>" {
     ...
     retry_policy = {
       policy = "<object_type_for_retry>"
       additional_properties = {
         <list_of_additional_retry_policy_parameters>
       }
       exchange_manager = {
         additional_properties = {
           <list_of_additional_storage_parameters>
         }
         service_s3 = {}
       }
     }
     ...
   }
   

   Where:

   • policy: Query retry method. The possible values are:

     • TASK: Retries the intermediate task within the query that caused worker failure.
     • QUERY: Retries all stages of the query in which the worker failed.

   • additional_properties: Additional query retry parameters in "<key>" = "<value>" format. For more information about parameters, see the Trino documentation.

   • exchangeManager: Exchange Manager storage parameters:

     • service_s3: Use an S3 storage to write data when retrying queries.
     • additional_properties: Additional Exchange Manager storage parameters in "<key>" = "<value>" format. For more information about parameters, see the Trino documentation.

3. Validate your configuration.

   1. In the command line, navigate to the directory that contains the current Terraform configuration files defining the infrastructure.

   2. Run this command:

      terraform validate
      

      Terraform will show any errors found in your configuration files.

4. Confirm resource changes.

   1. Run this command to view the planned changes:

      terraform plan
      

      If you described the configuration correctly, the terminal will display a list of the resources to update and their parameters. This is a verification step that does not apply changes to your resources.

   2. If everything looks correct, apply the changes:

      1. Run this command:

         terraform apply
         

      2. Confirm updating the resources.

      3. Wait for the operation to complete.

1. Get an IAM token for API authentication and place it in an environment variable:

   export IAM_TOKEN="<IAM_token>"
   

2. Create a file named body.json and paste the following code into it:

   {
     "updateMask": "<list_of_parameters_to_update>",
     "trino": {
       "retryPolicy": {
         "policy": "<object_type_for_retry>",
         "exchangeManager": {
           "storage": {
             "serviceS3": {}
           },
           "additionalProperties": {<additional_storage_parameters>}
         },
         "additionalProperties": {<additional_retry_parameters>}
       }
     }
   }
   

   Where:

   • updateMask: Comma-separated list of parameters to update.

     Warning

     When you update a cluster, all parameters of the object you are modifying will take their defaults unless explicitly provided in the request. To avoid this, list the settings you want to change in the updateMask parameter.

   • trino.retryPolicy: Fault-tolerant query execution parameters.

     • policy: Query retry method. The allowed values are:

       • TASK: Retries the intermediate task within the query that caused worker failure.
       • QUERY: Retries all stages of the query where worker failure occurred.

     • exchangeManager.additionalProperties: Additional Exchange Manager storage parameters in key: value format. For more information about parameters, see the Trino documentation.

     • additionalProperties: Additional parameters in key: value format. For more information about parameters, see the Trino documentation.

3. Use the Cluster.Update method and send the following request, e.g., via cURL:

   curl \
     --request PATCH \
     --header "Authorization: Bearer $IAM_TOKEN" \
     --url 'https://trino.api.cloud.yandex.net/managed-trino/v1/clusters/<cluster_ID>'
     --data '@body.json'
   

   You can get the cluster ID with the list of clusters in the folder.

4. Check the server response to make sure your request was successful.

1. Get an IAM token for API authentication and place it in an environment variable:

   export IAM_TOKEN="<IAM_token>"
   

2. Clone the cloudapi repository:

   cd ~/ && git clone --depth=1 https://github.com/yandex-cloud/cloudapi
   

   Below, we assume the repository contents are stored in the ~/cloudapi/ directory.

3. Create a file named body.json and paste the following code into it:

   {
     "cluster_id": "<cluster_ID>",
     "update_mask": {
       "paths": [
         <list_of_parameters_to_update>
       ]
     },
     "trino": {
       "retry_policy": {
         "policy": "<object_type_for_retry>",
         "exchange_manager": {
           "storage": {
             "service_s3": ""
           },
           "additional_properties": {<additional_storage_parameters>}
         },
         "additional_properties": {<additional_retry_parameters>}
       }
     }
   }
   

   Where:

   • cluster_id: Cluster ID.

     You can get the cluster ID with the list of clusters in the folder.

   • update_mask: List of settings you want to modify as an array of strings (paths[]).

     Format for listing settings

     "update_mask": {
       "paths": [
         "<setting_1>",
         "<setting_2>",
         ...
         "<setting_N>"
       ]
     }
     

     Warning

     When you update a cluster, all parameters of the object you are modifying will take their defaults unless explicitly provided in the request. To avoid this, list the settings you want to change in the update_mask parameter.

   • trino.retry_policy: Fault-tolerant query execution parameters.

     • policy: Query retry method. The allowed values are:

       • TASK: Retries the intermediate task within the query that caused worker failure.
       • QUERY: Retries all stages of the query where worker failure occurred.

     • exchange_manager.additional_properties: Additional Exchange Manager storage parameters in key: value format. For more information about parameters, see the Trino documentation.

     • additional_properties: Additional parameters in key: value format. For more information about parameters, see the Trino documentation.

4. Use the ClusterService.Update call and send the following request, e.g., via gRPCurl:

   grpcurl \
     -format json \
     -import-path ~/cloudapi/ \
     -import-path ~/cloudapi/third_party/googleapis/ \
     -proto ~/cloudapi/yandex/cloud/trino/v1/cluster_service.proto \
     -rpc-header "Authorization: Bearer $IAM_TOKEN" \
     -d @ \
     trino.api.cloud.yandex.net:443 \
     yandex.cloud.trino.v1.ClusterService.Update \
     < body.json
   

5. Check the server response to make sure your request was successful.

If you do not have the Yandex Cloud CLI installed yet, install and initialize it.

By default, the CLI uses the folder specified when creating the profile. To change the default folder, use the yc config set folder-id <folder_ID> command. You can also set a different folder for any specific command using the --folder-name or --folder-id parameter.

To change the configuration of the coordinator and workers:

1. View the description of the CLI command for updating a cluster:

   yc managed-trino cluster update --help
   

2. Run this command to change the configuration of the coordinator and workers:

   yc managed-trino cluster update <cluster_name_or_ID> \
     --coordinator resource-preset-id=<host_class> \
     --worker count=<number_of_instances>,`
             `min-count=<minimum_number_of_instances>,`
             `max-count=<maximum_number_of_instances>,`
             `resource-preset-id=<host_class>
   

   Where:

   • --coordinator: Coordinator configuration.

     • resource-preset-id: Class of coordinator hosts.

   • --worker: Worker configuration:

     • resource-preset-id: Class of worker hosts.
     • count: Number of workers.
     • min-count: Minimum number of workers.
     • max-count: Maximum number of workers.

     For worker count to automatically vary based on load, use min-count and max-count. If you need to set a fixed number of workers, use count.

   You can get the cluster name and ID with the list of clusters in the folder.

1. Open the current Terraform configuration file describing your infrastructure.

   For more information about creating this file, see this guide.

2. Edit the coordinator and worker configuration under coordinator and worker, respectively:

   resource "yandex_trino_cluster" "<cluster_name>" {
     ...
     coordinator = {
       resource_preset_id = "<class_of_computing_resources>"
     }
     
     worker = {
       fixed_scale = {
         count = <number_of_instances>
       }
       auto_scale = {
         max_count=<minimum_number_of_instances>
         min_count=<maximum_number_of_instances>
       }
       resource_preset_id = "<class_of_computing_resources>"
     }
     ...
   }
   

   Where:

   • coordinator: Coordinator configuration.

     • resource_preset_id: Class of coordinator hosts.

   • worker: Worker configuration:

     • resource_preset_id: Class of worker hosts.

     • fixed_scale: Fixed number of workers.

       • count: Number of workers

     • auto_scale: Worker number autoscaling.

       • min_count: Minimum number of workers.
       • max_count: Maximum number of workers.

     For worker count to automatically vary based on load, use the auto_scale section and set the minimum and maximum values. For a fixed number of workers, use the fixed_scale section and specify the required value.

3. Validate your configuration.

   1. In the command line, navigate to the directory that contains the current Terraform configuration files defining the infrastructure.

   2. Run this command:

      terraform validate
      

      Terraform will show any errors found in your configuration files.

4. Confirm resource changes.

   1. Run this command to view the planned changes:

      terraform plan
      

      If you described the configuration correctly, the terminal will display a list of the resources to update and their parameters. This is a verification step that does not apply changes to your resources.

   2. If everything looks correct, apply the changes:

      1. Run this command:

         terraform apply
         

      2. Confirm updating the resources.

      3. Wait for the operation to complete.

1. Get an IAM token for API authentication and place it in an environment variable:

   export IAM_TOKEN="<IAM_token>"
   

2. Create a file named body.json and paste the following code into it:

   {
     "updateMask": "<list_of_parameters_to_update>",
     "trino": {
       "coordinatorConfig": {
         "resources": {
           "resourcePresetId": "<host_class>"
         }
       },
       "workerConfig": {
         "resources": {
           "resourcePresetId": "<host_class>"
         },
         "scalePolicy": {
           "fixedScale": {
             "count": "<number_of_instances>"
           },
           "autoScale": {
             "minCount": "<minimum_number_of_instances>",
             "maxCount": "<maximum_number_of_instances>"
           }
         }
       }
     }
   }
   

   Where:

   • updateMask: Comma-separated list of parameters to update.

     Warning

     When you update a cluster, all parameters of the object you are modifying will take their defaults unless explicitly provided in the request. To avoid this, list the settings you want to change in the updateMask parameter.

   • trino.coordinatorConfig: Coordinator configuration.

     • resources.resourcePresetId: Class of coordinator hosts.

   • trino.workerConfig: Worker configuration:

     • resources.resourcePresetId: Class of worker hosts.

     • scalePolicy.fixedScale: Fixed number of workers.

       • count: Number of workers.

     • scalePolicy.autoScale: Worker number autoscaling.

       • minCount: Minimum number of workers.
       • maxCount: Maximum number of workers.

     For worker count to automatically vary based on load, use the scalePolicy.autoScale setting to set the minimum and maximum values. For a fixed number of workers, use the scalePolicy.fixedScale setting to set the required value.

3. Use the Cluster.Update method and send the following request, e.g., via cURL:

   curl \
     --request PATCH \
     --header "Authorization: Bearer $IAM_TOKEN" \
     --url 'https://trino.api.cloud.yandex.net/managed-trino/v1/clusters/<cluster_ID>'
     --data '@body.json'
   

   You can get the cluster ID with the list of clusters in the folder.

4. Check the server response to make sure your request was successful.

1. Get an IAM token for API authentication and place it in an environment variable:

   export IAM_TOKEN="<IAM_token>"
   

2. Clone the cloudapi repository:

   cd ~/ && git clone --depth=1 https://github.com/yandex-cloud/cloudapi
   

   Below, we assume the repository contents are stored in the ~/cloudapi/ directory.

3. Create a file named body.json and paste the following code into it:

   {
     "cluster_id": "<cluster_ID>",
     "update_mask": {
       "paths": [
         <list_of_parameters_to_update>
       ]
     },
     "trino": {
       "coordinator_config": {
         "resources": {
           "resource_preset_id": "<host_class>"
         }
       },
       "worker_config": {
         "resources": {
           "resource_preset_id": "<host_class>"
         },
         "scale_policy": {
           "fixed_scale": {
             "count": "<number_of_instances>"
           },
           "auto_scale": {
             "min_count": "<minimum_number_of_instances>",
             "max_count": "<maximum_number_of_instances>"
           }
         }
       }
     }
   }
   

   Where:

   • cluster_id: Cluster ID.

     You can get the cluster ID with the list of clusters in the folder.

   • update_mask: List of settings you want to modify as an array of strings (paths[]).

     Format for listing settings

     "update_mask": {
       "paths": [
         "<setting_1>",
         "<setting_2>",
         ...
         "<setting_N>"
       ]
     }
     

     Warning

     When you update a cluster, all parameters of the object you are modifying will take their defaults unless explicitly provided in the request. To avoid this, list the settings you want to change in the update_mask parameter.

   • trino.coordinator_config": Coordinator configuration.

     • resources.resource_preset_id: Class of coordinator hosts.

   • trino.worker_config: Worker configuration:

     • resources.resource_preset_id: Class of worker hosts.

     • scale_policy.fixed_scale: Fixed number of workers.

       • count: Number of workers.

     • scale_policy.auto_scale: Worker number autoscaling.

       • minCount: Minimum number of workers.
       • maxCount: Maximum number of workers.

     For worker count to automatically vary based on load, use the scale_policy.auto_scale setting to set the minimum and maximum values. For a fixed number of workers, use the scale_policy.fixed_scale setting to set the required value.

4. Use the ClusterService.Update call and send the following request, e.g., via gRPCurl:

   grpcurl \
     -format json \
     -import-path ~/cloudapi/ \
     -import-path ~/cloudapi/third_party/googleapis/ \
     -proto ~/cloudapi/yandex/cloud/trino/v1/cluster_service.proto \
     -rpc-header "Authorization: Bearer $IAM_TOKEN" \
     -d @ \
     trino.api.cloud.yandex.net:443 \
     yandex.cloud.trino.v1.ClusterService.Update \
     < body.json
   

5. Check the server response to make sure your request was successful.

If you do not have the Yandex Cloud CLI installed yet, install and initialize it.

By default, the CLI uses the folder specified when creating the profile. To change the default folder, use the yc config set folder-id <folder_ID> command. You can also set a different folder for any specific command using the --folder-name or --folder-id parameter.

To change additional cluster settings:

1. View the description of the CLI command for updating a cluster:

   yc managed-trino cluster update --help
   

2. Update additional cluster settings using this command:

   yc managed-trino cluster update <cluster_name_or_ID> \
     --deletion-protection \
     --maintenance-window type=<maintenance_type>,`
                         `day=<day_of_week>,`
                         `hour=<hour> \
     --log-enabled \
     --log-folder-id <folder_ID> \
     --log-group-id <log_group_ID> \
     --log-min-level <logging_level>
   

   Where:

   • --deletion-protection: Enables cluster protection against accidental deletion.

     Even with deletion protection enabled, one can still connect to the cluster manually and delete the data.

   • --maintenance-window: Maintenance window settings (including for disabled clusters), where type is the maintenance type:

     • anytime: At any time (default).
     • weekly: On a schedule. For this value, also specify the following:
       • day: Day of week, i.e., MON, TUE, WED, THU, FRI, SAT, or SUN.
       • hour: Hour of day (UTC), from 1 to 24.

   • Logging parameters:

     • --log-enabled: Enables logging. Logs generated by Trino components will be sent to Yandex Cloud Logging.

     • --log-folder-id: Folder ID. Logs will be written to the default log group for this folder.

     • --log-group-id: Custom log group ID.

       You can specify only one of the parameters: --log-folder-id or --log-group-id.

     • --log-min-level: Minimum logging level. Possible values: TRACE, DEBUG, INFO (default), WARN, ERROR, and FATAL.

   You can get the cluster name and ID with the list of clusters in the folder.

1. Open the current Terraform configuration file describing your infrastructure.

   For more information about creating this file, see this guide.

2. To enable cluster protection against accidental deletion, add the deletion_protection = true parameter:

   resource "yandex_trino_cluster" "<cluster_name>" {
     ...
     deletion_protection = true
     ...
   }
   

   Where deletion_protection is protection against accidental cluster deletion: true or false.

   Even with deletion protection enabled, one can still connect to the cluster manually and delete the data.

3. To change maintenance time (including for disabled clusters), add the maintenance_window section to the cluster description:

   resource "yandex_trino_cluster" "<cluster_name>" {
     ...
     maintenance_window = {
       type = <maintenance_type>
       day  = <day_of_week>
       hour = <hour>
     }
     ...
   }
   

   Where:

   • type: Maintenance type. The possible values include:
     • ANYTIME: Anytime
     • WEEKLY: On a schedule
   • day: Day of week for the WEEKLY type, i.e., MON, TUE, WED, THU, FRI, SAT, or SUN.
   • hour: UTC hour for the WEEKLY type, from 1 to 24.

4. To enable sending Trino logs to Yandex Cloud Logging, add the logging section to the cluster description:

   resource "yandex_trino_cluster" "<cluster_name>" {
     ...
     logging = {
       enabled   = <enable_logging>
       folder_id = <folder_ID>
       min_level = "<logging_level>"
     }
     ...
   }
   

   Where:

   • enabled: Enables logging, true or false.

   • folder_id: Folder ID. Logs will be written to the default log group for this folder.

   • log_group_id: Custom log group ID. Logs will be written to this group.

     You can specify only one of the parameters: folder_id or log_group_id.

   • min_level: Minimum logging level. Possible values: TRACE, DEBUG, INFO (default), WARN, ERROR, and FATAL.

5. Validate your configuration.

   1. In the command line, navigate to the directory that contains the current Terraform configuration files defining the infrastructure.

   2. Run this command:

      terraform validate
      

      Terraform will show any errors found in your configuration files.

6. Confirm resource changes.

   1. Run this command to view the planned changes:

      terraform plan
      

      If you described the configuration correctly, the terminal will display a list of the resources to update and their parameters. This is a verification step that does not apply changes to your resources.

   2. If everything looks correct, apply the changes:

      1. Run this command:

         terraform apply
         

      2. Confirm updating the resources.

      3. Wait for the operation to complete.

1. Get an IAM token for API authentication and place it in an environment variable:

   export IAM_TOKEN="<IAM_token>"
   

2. Create a file named body.json and paste the following code into it:

   {
     "updateMask": "<list_of_parameters_to_update>",
     "deletionProtection": "<deletion_protection>",
     "logging": {
       "enabled": "<use_of_logging>",
       "folderId": "<folder_ID>",
       "logGroupId": "<log_group_ID>",
       "minLevel": "<logging_level>"
     },
     "maintenanceWindow": {
       "weeklyMaintenanceWindow": {
         "day": "<day_of_week>",
         "hour": "<hour>"
       }
     }
   }
   

   Where:

   • updateMask: Comma-separated list of parameters to update.

     Warning

     When you update a cluster, all parameters of the object you are modifying will take their defaults unless explicitly provided in the request. To avoid this, list the settings you want to change in the updateMask parameter.

   • deletionProtection: Cluster protection from accidental deletion, true or false.

     Even if it is enabled, one can still connect to the cluster manually and delete it.

   • logging: Logging parameters:

     • enabled: Enables logging. Logs generated by Trino components will be sent to Yandex Cloud Logging. The possible values are true or false.

     • folderId: Folder ID. Logs will be written to the default log group for this folder.

     • logGroupId: Custom log group ID.

       You can specify only one of the parameters: folderId or logGroupId.

     • minLevel: Minimum logging level. Possible values: TRACE, DEBUG, INFO (default), WARN, ERROR, and FATAL.

   • maintenanceWindow: Maintenance window settings (including for disabled clusters). Provide one of the two parameters:

     • anytime: Maintenance takes place at any time.

     • weeklyMaintenanceWindow: Maintenance takes place once a week at the specified time:

       • day: Day of week for the WEEKLY type, i.e., MON, TUE, WED, THU, FRI, SAT, or SUN.
       • hour: Time of day (UTC) for the WEEKLY type, from 1 to 24.

3. Use the Cluster.Update method and send the following request, e.g., via cURL:

   curl \
     --request PATCH \
     --header "Authorization: Bearer $IAM_TOKEN" \
     --url 'https://trino.api.cloud.yandex.net/managed-trino/v1/clusters/<cluster_ID>'
     --data '@body.json'
   

   You can get the cluster ID with the list of clusters in the folder.

4. Check the server response to make sure your request was successful.

1. Get an IAM token for API authentication and place it in an environment variable:

   export IAM_TOKEN="<IAM_token>"
   

2. Clone the cloudapi repository:

   cd ~/ && git clone --depth=1 https://github.com/yandex-cloud/cloudapi
   

   Below, we assume the repository contents are stored in the ~/cloudapi/ directory.

3. Create a file named body.json and paste the following code into it:

   {
     "cluster_id": "<cluster_ID>",
     "update_mask": {
       "paths": [
         <list_of_parameters_to_update>
       ]
     },
     "deletion_protection": "<deletion_protection>",
     "logging": {
       "enabled": "<use_of_logging>",
       "folder_id": "<folder_ID>",
       "log_group_id": "<log_group_ID>",
       "min_level": "<logging_level>"
     },
     "maintenance_window": {
       "weekly_maintenance_window": {
         "day": "<day_of_week>",
         "hour": "<hour>"
       }
     }
   }
   

   Where:

   • cluster_id: Cluster ID.

     You can get the cluster ID with the list of clusters in the folder.

   • update_mask: List of settings you want to modify as an array of strings (paths[]).

     Format for listing settings

     "update_mask": {
       "paths": [
         "<setting_1>",
         "<setting_2>",
         ...
         "<setting_N>"
       ]
     }
     

     Warning

     When you update a cluster, all parameters of the object you are modifying will take their defaults unless explicitly provided in the request. To avoid this, list the settings you want to change in the update_mask parameter.

   • deletion_protection: Cluster protection from accidental deletion, true or false.

     Even with deletion protection enabled, one can still connect to the cluster manually and delete the data.

   • logging: Logging parameters:

     • enabled: Enables logging. Logs generated by Trino components will be sent to Yandex Cloud Logging. The possible values are true or false.

     • folder_id: Folder ID. Logs will be written to the default log group for this folder.

     • log_group_id: Custom log group ID.

       You can specify only one of the parameters: folderId or logGroupId.

     • min_level: Minimum logging level. Possible values: TRACE, DEBUG, INFO (default), WARN, ERROR, and FATAL.

   • maintenance_window: Maintenance window settings (including for disabled clusters). Provide one of the two parameters:

     • anytime: Maintenance takes place at any time.

     • weekly_maintenance_window: Maintenance takes place once a week at the specified time:

       • day: Day of week for the WEEKLY type, i.e., MON, TUE, WED, THU, FRI, SAT, or SUN.
       • hour: Time of day (UTC) for the WEEKLY type, from 1 to 24.

4. Use the ClusterService.Update call and send the following request, e.g., via gRPCurl:

   grpcurl \
     -format json \
     -import-path ~/cloudapi/ \
     -import-path ~/cloudapi/third_party/googleapis/ \
     -proto ~/cloudapi/yandex/cloud/trino/v1/cluster_service.proto \
     -rpc-header "Authorization: Bearer $IAM_TOKEN" \
     -d @ \
     trino.api.cloud.yandex.net:443 \
     yandex.cloud.trino.v1.ClusterService.Update \
     < body.json
   

5. View the server response to make sure your request was successful.