gcloud: Wed Mar 8 10:34:05 UTC 2023

gcloud/metastore/services/update

@@ -3,12 +3,16 @@ NAME
 
 SYNOPSIS
     gcloud metastore services update (SERVICE : --location=LOCATION) [--async]
-        [--port=PORT] [--tier=TIER] [--update-labels=[KEY=VALUE,...]]
+        [--port=PORT] [--update-labels=[KEY=VALUE,...]]
         [--clear-labels | --remove-labels=[KEY,...]]
+        [--instance-size=INSTANCE_SIZE | --scaling-factor=SCALING_FACTOR
+          | --tier=TIER]
         [--kerberos-principal=KERBEROS_PRINCIPAL
           --keytab=KEYTAB --krb5-config=KRB5_CONFIG]
         [--maintenance-window-day=MAINTENANCE_WINDOW_DAY
           --maintenance-window-hour=MAINTENANCE_WINDOW_HOUR]
+        [--update-auxiliary-versions-from-file=UPDATE_AUXILIARY_VERSIONS_FROM_FILE | --add-auxiliary-versions=[ADD_AUXILIARY_VERSIONS,
+          ...] --clear-auxiliary-versions]
         [--update-hive-metastore-configs-from-file=UPDATE_HIVE_METASTORE_CONFIGS_FROM_FILE | --update-hive-metastore-configs=[UPDATE_HIVE_METASTORE_CONFIGS,
           ...] --clear-hive-metastore-configs
           | --remove-hive-metastore-configs=[REMOVE_HIVE_METASTORE_CONFIGS,
@@ -70,18 +74,6 @@ FLAGS
      --port=PORT
         The TCP port on which the Metastore service will listen.
 
-     --tier=TIER
-        The tier of the service. TIER must be one of:
-
-         developer
-            The developer tier provides limited scalability and no fault
-            tolerance. Good for low-cost proof-of-concept.
-
-         enterprise
-            The enterprise tier provides multi-zone high availability, and
-            sufficient scalability for enterprise-level Dataproc Metastore
-            workloads.
-
      --update-labels=[KEY=VALUE,...]
         List of label KEY=VALUE pairs to update. If a label exists, its value
         is modified. Otherwise, a new label is created.
@@ -111,6 +103,46 @@ FLAGS
           silently ignored. If --update-labels is also specified then
           --update-labels is applied first.
 
+     The instance size of the Dataproc Metastore instance.
+
+     At most one of these can be specified:
+
+       --instance-size=INSTANCE_SIZE
+          The instance size of the service. INSTANCE_SIZE must be one of:
+
+           extra_large
+              Extra large instance size, maps to a scaling factor of 6.0.
+
+           extra_small
+              Extra small instance size, maps to a scaling factor of 0.1.
+
+           large
+              Large instance size, maps to a scaling factor of 3.0.
+
+           medium
+              Medium instance size, maps to a scaling factor of 1.0.
+
+           small
+              Small instance size, maps to a scaling factor of 0.5.
+
+       --scaling-factor=SCALING_FACTOR
+          The scaling factor of the service. This should be a float in the
+          range [0.1,6.0]. If the value is less than 1.0, then it should be a
+          multiple of 0.1. If the value is greater than 1.0, then it should be
+          a whole number.
+
+       --tier=TIER
+          The tier of the service. TIER must be one of:
+
+           developer
+              The developer tier provides limited scalability and no fault
+              tolerance. Good for low-cost proof-of-concept.
+
+           enterprise
+              The enterprise tier provides multi-zone high availability, and
+              sufficient scalability for enterprise-level Dataproc Metastore
+              workloads.
+
      Information used to configure the Hive metastore service as a service
      principal in a Kerberos realm.
 
@@ -148,6 +180,50 @@ FLAGS
           This flag argument must be specified if any of the other arguments in
           this group are specified.
 
+     Auxiliary versions configuration for the Dataproc Metastore service. When
+     specified, a secondary Hive metastore service is created along with the
+     primary service.
+
+    At most one of these can be specified:
+
+         --update-auxiliary-versions-from-file=UPDATE_AUXILIARY_VERSIONS_FROM_FILE
+            Path to a YAML file containing the auxiliary versions configuration
+            for Dataproc Metastore instance. The file should contain a unique
+            auxiliary service name and auxiliary version that is lower than the
+            primary service version. The primary version's Hive metastore
+            configs are applied to the auxiliary version. Additional Hive
+            metastore configs can be specified for the auxiliary version using
+            "config_overrides". If a specified config property has already been
+            overridden in the primary Hive metastore version's configs, the
+            auxiliary version's override takes precedence. The contents of the
+            file should be structured as follows:
+
+            YAML:
+
+                  - name: aux-service1
+                    version: x.y.z
+                    config_overrides:
+                      key1: value1
+                      key2: value2
+                    ...
+                  - name: aux-service2
+                    version: x.y.z
+                    config_overrides:
+                      key1: value1
+                      key2: value2
+                    ...
+                  ...
+
+         --add-auxiliary-versions=[ADD_AUXILIARY_VERSIONS,...]
+            Comma-separated list of auxiliary Hive metastore versions to
+            deploy. Auxiliary Hive metastore versions must be less than the
+            primary Hive metastore service's version.
+
+         --clear-auxiliary-versions
+            Clears the existing auxiliary services attached to the primary Hive
+            metastore services. If --add-auxiliary-versions is also specified,
+            --clear-auxiliary-versions is applied first.
+
      Configuration properties specific to running Hive metastore software as
      the metastore service.