Package com.google.privacy.dlp.v2

Interface DataProfileAction.ExportOrBuilder

All Superinterfaces:
com.google.protobuf.MessageLiteOrBuilder, com.google.protobuf.MessageOrBuilder
All Known Implementing Classes:
DataProfileAction.Export, DataProfileAction.Export.Builder
Enclosing class:
DataProfileAction
public static interface DataProfileAction.ExportOrBuilder extends com.google.protobuf.MessageOrBuilder

  • Method Summary

    Modifier and Type
    Method
    Description
    BigQueryTable
    getProfileTable()
    Store all profiles to BigQuery
    BigQueryTableOrBuilder
    getProfileTableOrBuilder()
    Store all profiles to BigQuery
    BigQueryTable
    getSampleFindingsTable()
    Store sample [data profile findings][google.privacy.dlp.v2.DataProfileFinding] in an existing table or a new table in an existing dataset.
    BigQueryTableOrBuilder
    getSampleFindingsTableOrBuilder()
    Store sample [data profile findings][google.privacy.dlp.v2.DataProfileFinding] in an existing table or a new table in an existing dataset.
    boolean
    hasProfileTable()
    Store all profiles to BigQuery
    boolean
    hasSampleFindingsTable()
    Store sample [data profile findings][google.privacy.dlp.v2.DataProfileFinding] in an existing table or a new table in an existing dataset.

    Methods inherited from interface com.google.protobuf.MessageLiteOrBuilder

    isInitialized

    Methods inherited from interface com.google.protobuf.MessageOrBuilder

    findInitializationErrors, getAllFields, getDefaultInstanceForType, getDescriptorForType, getField, getInitializationErrorString, getOneofFieldDescriptor, getRepeatedField, getRepeatedFieldCount, getUnknownFields, hasField, hasOneof

  • Method Details

    • hasProfileTable

      boolean hasProfileTable()
       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](https://cloud.google.com/sensitive-data-protection/docs/analyze-data-profiles).
 * See [Sample queries for your BigQuery
 table](https://cloud.google.com/sensitive-data-protection/docs/analyze-data-profiles#sample_sql_queries).
 *  Data is inserted using [streaming
 insert](https://cloud.google.com/blog/products/bigquery/life-of-a-bigquery-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](https://cloud.google.com/sensitive-data-protection/docs/analyze-data-profiles#use_a_premade_report).
 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;
      Returns:
      Whether the profileTable field is set.

    • getProfileTable

      BigQueryTable getProfileTable()
       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](https://cloud.google.com/sensitive-data-protection/docs/analyze-data-profiles).
 * See [Sample queries for your BigQuery
 table](https://cloud.google.com/sensitive-data-protection/docs/analyze-data-profiles#sample_sql_queries).
 *  Data is inserted using [streaming
 insert](https://cloud.google.com/blog/products/bigquery/life-of-a-bigquery-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](https://cloud.google.com/sensitive-data-protection/docs/analyze-data-profiles#use_a_premade_report).
 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;
      Returns:
      The profileTable.

    • getProfileTableOrBuilder

      BigQueryTableOrBuilder getProfileTableOrBuilder()
       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](https://cloud.google.com/sensitive-data-protection/docs/analyze-data-profiles).
 * See [Sample queries for your BigQuery
 table](https://cloud.google.com/sensitive-data-protection/docs/analyze-data-profiles#sample_sql_queries).
 *  Data is inserted using [streaming
 insert](https://cloud.google.com/blog/products/bigquery/life-of-a-bigquery-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](https://cloud.google.com/sensitive-data-protection/docs/analyze-data-profiles#use_a_premade_report).
 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;

    • hasSampleFindingsTable

      boolean hasSampleFindingsTable()
       Store sample [data profile
 findings][google.privacy.dlp.v2.DataProfileFinding] in an existing table
 or a new table in an existing dataset. Each regeneration will result in
 new rows in BigQuery. Data is inserted using [streaming
 insert](https://cloud.google.com/blog/products/bigquery/life-of-a-bigquery-streaming-insert)
 and so data may be in the buffer for a period of time after the profile
 has finished.
      .google.privacy.dlp.v2.BigQueryTable sample_findings_table = 2;
      Returns:
      Whether the sampleFindingsTable field is set.

    • getSampleFindingsTable

      BigQueryTable getSampleFindingsTable()
       Store sample [data profile
 findings][google.privacy.dlp.v2.DataProfileFinding] in an existing table
 or a new table in an existing dataset. Each regeneration will result in
 new rows in BigQuery. Data is inserted using [streaming
 insert](https://cloud.google.com/blog/products/bigquery/life-of-a-bigquery-streaming-insert)
 and so data may be in the buffer for a period of time after the profile
 has finished.
      .google.privacy.dlp.v2.BigQueryTable sample_findings_table = 2;
      Returns:
      The sampleFindingsTable.

    • getSampleFindingsTableOrBuilder

      BigQueryTableOrBuilder getSampleFindingsTableOrBuilder()
       Store sample [data profile
 findings][google.privacy.dlp.v2.DataProfileFinding] in an existing table
 or a new table in an existing dataset. Each regeneration will result in
 new rows in BigQuery. Data is inserted using [streaming
 insert](https://cloud.google.com/blog/products/bigquery/life-of-a-bigquery-streaming-insert)
 and so data may be in the buffer for a period of time after the profile
 has finished.
      .google.privacy.dlp.v2.BigQueryTable sample_findings_table = 2;