gcloud alpha data-catalog entries update - update a Data Catalog entry

gcloud alpha data-catalog entries update[ENTRY :--entry-group=ENTRY_GROUP--location=LOCATION][--description=DESCRIPTION][--display-name=DISPLAY_NAME][--lookup-entry=RESOURCE][--add-file-patterns=[PATTERN,…]--clear-file-patterns    |--remove-file-patterns=[PATTERN,…]][--schema=[COLUMN_NAME=COLUMN_TYPE,…]    |--schema-from-file=PATH_TO_FILE][GCLOUD_WIDE_FLAG …]

Update a Data Catalog entry. The entry to update can either be specifieddirectly, or the--lookup-entry flag may be used to update theentry corresponding to the lookup of the given resource.

gcloudalphadata-catalogentriesupdateentry1--location=global--entry-group=@pubsub--schema="column1=type1,column2=type2"

To update the schema of a Cloud Pub/Sub entry from a file, run:

gcloudalphadata-catalogentriesupdateentry1--location=global--entry-group=@pubsub--schema-from-file="/tmp/schema.json"

To lookup the entry of a Cloud Pub/Sub topic by its SQL name and update itsschema in one command, run:

gcloudalphadata-catalogentriesupdate--lookup-entry='pubsub.topic.`my-project1`.topic1'--schema="column1=type1,column2=type2"

Entry resource - Entry to update. The arguments in this group can be used tospecify the attributes of this resource. (NOTE) Some attributes are not givenarguments in this group but can be set in other ways.

To set theproject attribute:

• provide the argumententry on the command line with a fullyspecified name;
• provide the argument--project on the command line;
• set the propertycore/project.

ENTRY

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

To set theentry attribute:

• provide the argumententry on the command line.

This positional argument must be specified if any of the other arguments in thisgroup are specified.

--entry-group=ENTRY_GROUP

Entry group of the entry.To set theentry-group attribute:

• provide the argumententry on the command line with a fullyspecified name;
• provide the argument--entry-group on the command line.

--location=LOCATION

Location of the entry.To set thelocation attribute:

• provide the argumententry on the command line with a fullyspecified name;
• provide the argument--location on the command line.

--description=DESCRIPTION

Textual description of the entry.

--display-name=DISPLAY_NAME

Human-readable name for the entry.

--lookup-entry=RESOURCE

The name of the target resource whose entry to update. This can be either theGoogle Cloud Platform resource name or the SQL name of a Google Cloud Platformresource. This flag allows one to update the entry corresponding to the lookupof the given resource, without needing to specify the entry directly.

--add-file-patterns=[PATTERN,…]

A list of file patterns to add to the current list.

At most one of these can be specified:

--clear-file-patterns

If specified, clear the current list of file patterns.

--remove-file-patterns=[PATTERN,…]

A list of file patterns to remove from the current list.

New column schema for the entry. A schema consists of a list of column namesalong with their types, descriptions, modes, and nested subcolumns. For example:

-column:first_namedescription:Firstnamemode:REQUIREDtype:STRING-column:last_namedescription:Lastnamemode:REQUIREDtype:STRING-column:addressesdescription:Addressesmode:REPEATEDtype:RECORDsubcolumns:-column:citydescription:Citymode:NULLABLEtype:STRING-column:statedescription:Statemode:NULLABLEtype:STRING

At most one of these can be specified:

--schema=[COLUMN_NAME=COLUMN_TYPE,…]

Inline schema for the entry. When specifying a schema via this argument, onlycolumn names and types should be provided. Column modes will default toNULLABLE, and column descriptions and nested subcolumns are not supported.

--schema-from-file=PATH_TO_FILE

Path to a JSON or YAML file containing the schema for the entry. This can beused to specify schemas with column descriptions, column modes other thanNULLABLE, and nested subcolumns. Use a full or relative path to a local filecontaining the value of schema.

Run$gcloud help for details.