imjasonh/gcloud-help
1
0
Fork 0
mirror of https://github.com/imjasonh/gcloud-help synced 2026-07-10 03:16:46 +00:00
Code Activity
gcloud-help/gcloud/metastore/services/create
Automated 1456dab6c7 gcloud: Tue Mar 1 04:29:52 UTC 2022
2022-03-01 04:29:52 +00:00

226 lines
8.9 KiB
Text
Raw Blame History

NAME
gcloud metastore services create - create a Dataproc Metastore service
SYNOPSIS
gcloud metastore services create (SERVICE : --location=LOCATION) [--async]
[--encryption-kms-key=ENCRYPTION_KMS_KEY]
[--hive-metastore-version=HIVE_METASTORE_VERSION]
[--labels=[KEY=VALUE,...]] [--network=NETWORK; default="default"]
[--port=PORT; default=9083]
[--release-channel=RELEASE_CHANNEL; default="stable"] [--tier=TIER]
[--hive-metastore-configs=KEY=VALUE
| --hive-metastore-configs-from-file=HIVE_METASTORE_CONFIGS_FROM_FILE]
[--kerberos-principal=KERBEROS_PRINCIPAL
--keytab=KEYTAB --krb5-config=KRB5_CONFIG]
[--maintenance-window-day=MAINTENANCE_WINDOW_DAY
--maintenance-window-hour=MAINTENANCE_WINDOW_HOUR]
[GCLOUD_WIDE_FLAG ...]
DESCRIPTION
Create a new Dataproc Metastore service with the given name and
configurations.
If run asynchronously with --async, exits after printing one operation name
that can be used to poll the status of the creation via:
gcloud metastore operations describe
EXAMPLES
To create a Dataproc Metastore service with the name my-metastore-service
in location us-central using a non default port 9090, run:
$ gcloud metastore services create my-metastore-service \
--location=us-central1 --port=9090
To create a Dataproc Metastore service with the name my-metastore-service
in location us-central using a non default network foo, run:
$ gcloud metastore services create my-metastore-service \
--location=us-central1 --network=foo
POSITIONAL ARGUMENTS
Service resource - Arguments and flags that specify the Dataproc Metastore
service you want to create. The arguments in this group can be used to
specify the attributes of this resource. (NOTE) Some attributes are not
given arguments in this group but can be set in other ways. To set the
project attribute:
◆ provide the argument service on the command line with a fully
specified name;
◆ set the property core/project;
◆ provide the argument --project on the command line.
This must be specified.
SERVICE
ID of the service or fully qualified identifier for the service. To
set the service attribute:
▸ provide the argument service on the command line.
This positional must be specified if any of the other arguments in
this group are specified.
--location=LOCATION
The location of the Dataproc Metastore service.
If not specified, will use default metastore/location.
To set the location attribute:
▸ provide the argument service on the command line with a fully
specified name;
▸ provide the argument --location on the command line;
▸ set the property metastore/location.
FLAGS
--async
Return immediately, without waiting for the operation in progress to
complete.
--encryption-kms-key=ENCRYPTION_KMS_KEY
The name of the Cloud KMS key to use for customer data encryption.
Cannot be changed once the service is created. Mutually exclusive with
flag --data-catalog-sync. This can be provided as a fully-qualified
URL, or a relative name in the form
projects/{project_id}/locations/{location}/keyRings/{key_ring_id}/cryptoKeys/{crypto_key_id}.
--hive-metastore-version=HIVE_METASTORE_VERSION
The Hive metastore schema version. The supported versions of a location
are listed via:
gcloud metastore locations describe
If unspecified, the default version chosen by the server will be used.
--labels=[KEY=VALUE,...]
List of label KEY=VALUE pairs to add.
Keys must start with a lowercase character and contain only hyphens
(-), underscores (_), lowercase characters, and numbers. Values must
contain only hyphens (-), underscores (_), lowercase characters, and
numbers.
Network configuration for the metastore service.
--network=NETWORK; default="default"
The name of the network on which the service can be accessed. This
can be the network's ID, fully-qualified URL, or relative name in the
form projects/{project_id}/global/networks/{network}. If unspecified,
the "default" network will be used.
--port=PORT; default=9083
The TCP port on which the Metastore service will listen. If
unspecified, the default port 9083 will be used.
--release-channel=RELEASE_CHANNEL; default="stable"
The release channel of the service. RELEASE_CHANNEL must be one of:
canary
The CANARY release channel contains the newest features, which may
be unstable and subject to unresolved issues with no known
workarounds. Services using the CANARY release channel are not
subject to any SLAs.
stable
The STABLE release channel contains features that are considered
stable and have been validated for production use.
--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.
Configuration properties specific to running Hive metastore software as
the metastore service.
At most one of these can be specified:
--hive-metastore-configs=KEY=VALUE
A mapping of Hive metastore configuration key-value pairs to apply
to the Hive metastore.
--hive-metastore-configs-from-file=HIVE_METASTORE_CONFIGS_FROM_FILE
Path to a XML file containing a mapping of Hive metastore
configuration key-value pairs to apply to the Hive metastore.
For example:
hive-site.xml
<configuration>
<property>
<name>hive.metastore.warehouse.dir</name>
<value>${test.warehouse.dir}</value>
<description></description>
</property>
</configuration>
Information used to configure the Hive metastore service as a service
principal in a Kerberos realm.
--kerberos-principal=KERBEROS_PRINCIPAL
A Kerberos principal that exists in the KDC to authenticate as. A
typical principal is of the form "primary/instance@REALM", but there
is no exact format.
This flag must be specified if any of the other arguments in this
group are specified.
--keytab=KEYTAB
A Kerberos keytab file that can be used to authenticate a service
principal with a Kerberos Key Distribution Center. This is a Secret
Manager secret version, and can be fully-qualified URL, or relative
name in the form
projects/{project_id}/secrets/{secret_id}/versions/{version_id}.
This flag must be specified if any of the other arguments in this
group are specified.
--krb5-config=KRB5_CONFIG
A Cloud Storage URI that specifies the path to a krb5.conf file. It
is of the form gs://{bucket_name}/path/krb5.conf, although the file
does not need to be named krb5.conf explicitly.
This flag must be specified if any of the other arguments in this
group are specified.
The one hour maintenance window that specifies when Dataproc Metastore may
perform system maintenance operation to the service, in UTC time.
--maintenance-window-day=MAINTENANCE_WINDOW_DAY
The day of week when the window starts, e.g., sun.
MAINTENANCE_WINDOW_DAY must be one of: fri, mon, sat, sun, thu, tue,
wed.
This flag must be specified if any of the other arguments in this
group are specified.
--maintenance-window-hour=MAINTENANCE_WINDOW_HOUR
The hour of day (0-23) when the window starts.
This flag must be specified if any of the other arguments in this
group are specified.
GCLOUD WIDE FLAGS
These flags are available to all commands: --access-token-file, --account,
--billing-project, --configuration, --flags-file, --flatten, --format,
--help, --impersonate-service-account, --log-http, --project, --quiet,
--trace-token, --user-output-enabled, --verbosity.
Run $ gcloud help for details.
API REFERENCE
This command uses the metastore/v1 API. The full documentation for this API
can be found at: https://cloud.google.com/dataproc-metastore/docs
NOTES
These variants are also available:
$ gcloud alpha metastore services create
$ gcloud beta metastore services create
View git blame Copy permalink