.TH "GCLOUD_ALPHA_BQ_DATASETS_UPDATE" 1



.SH "NAME"
.HP
gcloud alpha bq datasets update \- update a BigQuery dataset



.SH "SYNOPSIS"
.HP
\f5gcloud alpha bq datasets update\fR \fIDATASET\fR [\fB\-\-description\fR=\fIDESCRIPTION\fR] [\fB\-\-permissions\-file\fR=[\fIPERMISSIONS_FILE\fR,...]] [\fIGCLOUD_WIDE_FLAG\ ...\fR]



.SH "DESCRIPTION"

\fB(ALPHA)\fR Update a BigQuery dataset.



.SH "EXAMPLES"

The following command updates the description on a dataset with ID
\f5my\-dataset\fR

.RS 2m
$ gcloud alpha bq datasets update my\-dataset \e
    \-\-description 'My New Dataset Description'
.RE



.SH "POSITIONAL ARGUMENTS"

.RS 2m
.TP 2m

Dataset resource \- The BigQuery dataset you want to update. This represents a
Cloud resource. (NOTE) Some attributes are not given arguments in this group but
can be set in other ways.

To set the \f5project\fR attribute:
.RS 2m
.IP "\(em" 2m
provide the argument \f5dataset\fR on the command line with a fully specified
name;
.IP "\(em" 2m
provide the argument \f5\-\-project\fR on the command line;
.IP "\(em" 2m
set the property \f5core/project\fR.
.RE
.sp

This must be specified.


.RS 2m
.TP 2m
\fIDATASET\fR

ID of the dataset or fully qualified identifier for the dataset.

To set the \f5dataset\fR attribute:
.RS 2m
.IP "\(bu" 2m
provide the argument \f5dataset\fR on the command line.
.RE
.sp


.RE
.RE
.sp

.SH "FLAGS"

.RS 2m
.TP 2m
\fB\-\-description\fR=\fIDESCRIPTION\fR

Description of the dataset.

.TP 2m
\fB\-\-permissions\-file\fR=[\fIPERMISSIONS_FILE\fR,...]

A local yaml or JSON file containing the access permissions specifying who is
allowed to access the data.

YamlfFile should be specified the form:\e access:
.RS 2m
.IP "\(em" 2m
role: ROLE [access type]: ACCESS_VALUE
.IP "\(em" 2m
...
.RE
.sp

and JSON file should be specified in the form: {"access": [ { "role": "ROLE",
"[access type]": "ACCESS_VALUE" }, ... ]}

Where \f5access type\fR is one of: \f5domain\fR, \f5userByEmail\fR,
\f5specialGroup\fR or \f5view\fR.

If this field is not specified, BigQuery adds these default dataset access
permissions at creation time in :
.RS 2m
.IP "\(em" 2m
specialGroup=projectReaders, role=READER
.IP "\(em" 2m
specialGroup=projectWriters, role=WRITER
.IP "\(em" 2m
specialGroup=projectOwners, role=OWNER
.IP "\(em" 2m
userByEmail=[dataset creator email], role=OWNER
.RE
.sp

For more information on BigQuery permissions see:
https://cloud.google.com/bigquery/docs/access\-control


.RE
.sp

.SH "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 \fB$ gcloud help\fR for details.



.SH "API REFERENCE"

This command uses the \fBbigquery/v2\fR API. The full documentation for this API
can be found at: https://cloud.google.com/bigquery/



.SH "NOTES"

This command is currently in alpha and might change without notice. If this
command fails with API permission errors despite specifying the correct project,
you might be trying to access an API with an invitation\-only early access
allowlist.