gcloud healthcare dicom-stores export bq

gcloud healthcare dicom-stores export bq - export a Cloud Healthcare API API DICOM store to BigQuery

gcloud healthcare dicom-stores export bq (DICOM_STORE : --dataset=DATASET --location=LOCATION) --bq-table=BQ_TABLE [--async] [--overwrite-table] [--write-disposition=WRITE_DISPOSITION] [GCLOUD_WIDE_FLAG …]

gcloud healthcare dicom-stores export bq test-dicom-store --bq-table=bq://my-project.testdataset.testtable --dataset=test-dataset --write-disposition=write-truncate

To export the dicom-store test-dicom-store to the BigQuery table testtable in the dataset testdataset, appending any existing table, run:

gcloud healthcare dicom-stores export bq test-dicom-store --bq-table=bq://my-project.testdataset.testtable --dataset=test-dataset --write-disposition=write-append

DicomStore resource - Cloud Healthcare API DICOM store to export. 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 dicom_store 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.

DICOM_STORE

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

To set the dicom_store attribute:

• provide the argument dicom_store on the command line.

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

--dataset=DATASET

Cloud Healthcare dataset.

To set the dataset attribute:

• provide the argument dicom_store on the command line with a fully specified name;
• provide the argument --dataset on the command line.

--location=LOCATION

Google Cloud location.

To set the location attribute:

• provide the argument dicom_store on the command line with a fully specified name;
• provide the argument --location on the command line;
• set the property healthcare/location.

--bq-table=BQ_TABLE

The BigQuery table where the DICOM store should be written. If this table does not exist, a new table with the given name will be created.

--async

Return immediately, without waiting for the operation in progress to complete.

--overwrite-table

If the destination table already exists and this flag is TRUE, the table will be overwritten by the contents of the DICOM store. If the flag is not set and the destination table already exists, the export call returns an error.

--write-disposition=WRITE_DISPOSITION

Determines whether the existing table in the destination is to be overwritten or appended to. WRITE_DISPOSITION must be one of:

write-append

Append data to the existing table.

write-empty

Only export data if the destination table is empty.

write-truncate

Erase all existing data in a table before writing the instances.

Run $ gcloud help for details.