Class DataProfileAction.Export.Builder (3.64.0)

Stay organized with collections Save and categorize content based on your preferences.

If set, the detailed data profiles will be persisted to the location of your choice whenever updated.

Protobuf type google.privacy.dlp.v2.DataProfileAction.Export

Store all profiles to BigQuery.

• The system will create a new dataset and table for you if none are are provided. The dataset will be named sensitive_data_protection_discovery and table will be named discovery_profiles. This table will be placed in the same project as the container project running the scan. After the first profile is generated and the dataset and table are created, the discovery scan configuration will be updated with the dataset and table names.
• See Analyze data profiles stored in BigQuery.
• See Sample queries for your BigQuery table.
• Data is inserted using streaming insert and so data may be in the buffer for a period of time after the profile has finished.
  • The Pub/Sub notification is sent before the streaming buffer is guaranteed to be written, so data may not be instantly visible to queries by the time your topic receives the Pub/Sub notification.
  • The best practice is to use the same table for an entire organization so that you can take advantage of the provided Looker reports. If you use VPC Service Controls to define security perimeters, then you must use a separate table for each boundary.

.google.privacy.dlp.v2.BigQueryTable profile_table = 1;

Store all profiles to BigQuery.

• The system will create a new dataset and table for you if none are are provided. The dataset will be named sensitive_data_protection_discovery and table will be named discovery_profiles. This table will be placed in the same project as the container project running the scan. After the first profile is generated and the dataset and table are created, the discovery scan configuration will be updated with the dataset and table names.
• See Analyze data profiles stored in BigQuery.
• See Sample queries for your BigQuery table.
• Data is inserted using streaming insert and so data may be in the buffer for a period of time after the profile has finished.
  • The Pub/Sub notification is sent before the streaming buffer is guaranteed to be written, so data may not be instantly visible to queries by the time your topic receives the Pub/Sub notification.
  • The best practice is to use the same table for an entire organization so that you can take advantage of the provided Looker reports. If you use VPC Service Controls to define security perimeters, then you must use a separate table for each boundary.

.google.privacy.dlp.v2.BigQueryTable profile_table = 1;

Store all profiles to BigQuery.

• The system will create a new dataset and table for you if none are are provided. The dataset will be named sensitive_data_protection_discovery and table will be named discovery_profiles. This table will be placed in the same project as the container project running the scan. After the first profile is generated and the dataset and table are created, the discovery scan configuration will be updated with the dataset and table names.
• See Analyze data profiles stored in BigQuery.
• See Sample queries for your BigQuery table.
• Data is inserted using streaming insert and so data may be in the buffer for a period of time after the profile has finished.
  • The Pub/Sub notification is sent before the streaming buffer is guaranteed to be written, so data may not be instantly visible to queries by the time your topic receives the Pub/Sub notification.
  • The best practice is to use the same table for an entire organization so that you can take advantage of the provided Looker reports. If you use VPC Service Controls to define security perimeters, then you must use a separate table for each boundary.

.google.privacy.dlp.v2.BigQueryTable profile_table = 1;

Store all profiles to BigQuery.

• The system will create a new dataset and table for you if none are are provided. The dataset will be named sensitive_data_protection_discovery and table will be named discovery_profiles. This table will be placed in the same project as the container project running the scan. After the first profile is generated and the dataset and table are created, the discovery scan configuration will be updated with the dataset and table names.
• See Analyze data profiles stored in BigQuery.
• See Sample queries for your BigQuery table.
• Data is inserted using streaming insert and so data may be in the buffer for a period of time after the profile has finished.
  • The Pub/Sub notification is sent before the streaming buffer is guaranteed to be written, so data may not be instantly visible to queries by the time your topic receives the Pub/Sub notification.
  • The best practice is to use the same table for an entire organization so that you can take advantage of the provided Looker reports. If you use VPC Service Controls to define security perimeters, then you must use a separate table for each boundary.

.google.privacy.dlp.v2.BigQueryTable profile_table = 1;

Store all profiles to BigQuery.

• The system will create a new dataset and table for you if none are are provided. The dataset will be named sensitive_data_protection_discovery and table will be named discovery_profiles. This table will be placed in the same project as the container project running the scan. After the first profile is generated and the dataset and table are created, the discovery scan configuration will be updated with the dataset and table names.
• See Analyze data profiles stored in BigQuery.
• See Sample queries for your BigQuery table.
• Data is inserted using streaming insert and so data may be in the buffer for a period of time after the profile has finished.
  • The Pub/Sub notification is sent before the streaming buffer is guaranteed to be written, so data may not be instantly visible to queries by the time your topic receives the Pub/Sub notification.
  • The best practice is to use the same table for an entire organization so that you can take advantage of the provided Looker reports. If you use VPC Service Controls to define security perimeters, then you must use a separate table for each boundary.

.google.privacy.dlp.v2.BigQueryTable profile_table = 1;

Store all profiles to BigQuery.

• The system will create a new dataset and table for you if none are are provided. The dataset will be named sensitive_data_protection_discovery and table will be named discovery_profiles. This table will be placed in the same project as the container project running the scan. After the first profile is generated and the dataset and table are created, the discovery scan configuration will be updated with the dataset and table names.
• See Analyze data profiles stored in BigQuery.
• See Sample queries for your BigQuery table.
• Data is inserted using streaming insert and so data may be in the buffer for a period of time after the profile has finished.
  • The Pub/Sub notification is sent before the streaming buffer is guaranteed to be written, so data may not be instantly visible to queries by the time your topic receives the Pub/Sub notification.
  • The best practice is to use the same table for an entire organization so that you can take advantage of the provided Looker reports. If you use VPC Service Controls to define security perimeters, then you must use a separate table for each boundary.

.google.privacy.dlp.v2.BigQueryTable profile_table = 1;

Store all profiles to BigQuery.

• The system will create a new dataset and table for you if none are are provided. The dataset will be named sensitive_data_protection_discovery and table will be named discovery_profiles. This table will be placed in the same project as the container project running the scan. After the first profile is generated and the dataset and table are created, the discovery scan configuration will be updated with the dataset and table names.
• See Analyze data profiles stored in BigQuery.
• See Sample queries for your BigQuery table.
• Data is inserted using streaming insert and so data may be in the buffer for a period of time after the profile has finished.
  • The Pub/Sub notification is sent before the streaming buffer is guaranteed to be written, so data may not be instantly visible to queries by the time your topic receives the Pub/Sub notification.
  • The best practice is to use the same table for an entire organization so that you can take advantage of the provided Looker reports. If you use VPC Service Controls to define security perimeters, then you must use a separate table for each boundary.

.google.privacy.dlp.v2.BigQueryTable profile_table = 1;

Store all profiles to BigQuery.

• The system will create a new dataset and table for you if none are are provided. The dataset will be named sensitive_data_protection_discovery and table will be named discovery_profiles. This table will be placed in the same project as the container project running the scan. After the first profile is generated and the dataset and table are created, the discovery scan configuration will be updated with the dataset and table names.
• See Analyze data profiles stored in BigQuery.
• See Sample queries for your BigQuery table.
• Data is inserted using streaming insert and so data may be in the buffer for a period of time after the profile has finished.
  • The Pub/Sub notification is sent before the streaming buffer is guaranteed to be written, so data may not be instantly visible to queries by the time your topic receives the Pub/Sub notification.
  • The best practice is to use the same table for an entire organization so that you can take advantage of the provided Looker reports. If you use VPC Service Controls to define security perimeters, then you must use a separate table for each boundary.

.google.privacy.dlp.v2.BigQueryTable profile_table = 1;