1
0
Fork 0
mirror of https://github.com/imjasonh/gcloud-help synced 2026-07-08 10:35:03 +00:00
gcloud-help/gcloud/metastore/services/query-metadata
2023-05-17 10:38:17 +00:00

83 lines
3.2 KiB
Text

NAME
gcloud metastore services query-metadata - execute a SQL query against a
Dataproc Metastore Service's metadata
SYNOPSIS
gcloud metastore services query-metadata (SERVICE : --location=LOCATION)
--query=QUERY [--format=FORMAT] [GCLOUD_WIDE_FLAG ...]
DESCRIPTION
Execute a SQL query against a Dataproc Metastore Service's metadata.
EXAMPLES
To query metadata against a Dataproc Metastore service with the name
my-metastore-service in location us-central1, and the sql query "show
tables;", run:
$ gcloud metastore services query-metadata my-metastore-service \
--location=us-central1 --query="show tables;"
POSITIONAL ARGUMENTS
Service resource - The service to query metadata. 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;
◆ provide the argument --project on the command line;
◆ set the property core/project.
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 argument must be specified if any of the other
arguments in this group are specified.
--location=LOCATION
Location to which the service belongs.
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.
REQUIRED FLAGS
--query=QUERY
Use Google Standard SQL query for Cloud Spanner and MySQL query syntax
for Cloud SQL. Cloud Spanner SQL is described at
https://cloud.google.com/spanner/docs/query-syntax)"
COMMONLY USED FLAGS
--format=FORMAT
Sets the format for printing command output resources. The default is a
command-specific human-friendly output format. If both core/format and
--format are specified, --format takes precedence. --format and
core/format both take precedence over core/default_format. The
supported formats are limited to: config, csv, default, diff, disable,
flattened, get, json, list, multi, none, object, table, text, value,
yaml. For more details run $ gcloud topic formats. Run $ gcloud config
set --help to see more information about core/format
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.
NOTES
These variants are also available:
$ gcloud alpha metastore services query-metadata
$ gcloud beta metastore services query-metadata