gcloud beta data-catalog entries create - create a Data Catalog entry

gcloud beta data-catalog entries create(ENTRY :--entry-group=ENTRY_GROUP--location=LOCATION)--gcs-file-patterns=[GCS_FILE_PATTERNS,…][--description=DESCRIPTION][--display-name=DISPLAY_NAME][--schema=[COLUMN_NAME=COLUMN_TYPE,…]    |--schema-from-file=PATH_TO_FILE][GCLOUD_WIDE_FLAG …]

Create a Data Catalog entry.

gcloudbetadata-catalogentriescreateentry1--location=us-central1--entry-group=group1--gcs-file-patterns="gs://bucket1/abc/*,gs://bucket1/file1"--display-name="analytics data"

To create an entry for a Google Cloud Storage fileset with an inline schema,run:

gcloudbetadata-catalogentriescreateentry1--location=us-central1--entry-group=group1--gcs-file-patterns="gs://bucket1/*"--display-name="sales data"--schema="qtr=STRING,sales=FLOAT,year=STRING"

To create an entry for a Google Cloud Storage fileset with a schema from a file,run:

gcloudbetadata-catalogentriescreateentry1--location=us-central1--entry-group=group1--gcs-file-patterns="gs://bucket1/*"--display-name="sales data"--schema-from-file=/tmp/schema.json

Entry resource - Entry to create. 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.

This must be specified.

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.

--gcs-file-patterns=[GCS_FILE_PATTERNS,…]

Patterns to identify a set of files in Google Cloud Storage. A star(*) may be used at the end of a pattern to match arbitrary filesbeginning with that pattern.

Examples of valid file patterns:

• gs://bucket_name/* - Matches all files in 'bucket_name'.
• gs://bucket_name/file* - Matches files prefixed by 'file' in'bucket_name'.
• gs://another_bucket/a.txt - Matches 'gs://another_bucket/a.txt'.

--description=DESCRIPTION

Textual description of the entry.

--display-name=DISPLAY_NAME

Human-readable name for the entry.

Column schema for the entry. A schema consists of a list of column names alongwith 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.