Package com.google.privacy.dlp.v2

Class DataProfileAction.Export.Builder

java.lang.Object
com.google.protobuf.AbstractMessageLite.Builder
com.google.protobuf.AbstractMessage.Builder<BuilderT>
com.google.protobuf.GeneratedMessage.Builder<DataProfileAction.Export.Builder>
com.google.privacy.dlp.v2.DataProfileAction.Export.Builder
All Implemented Interfaces:
DataProfileAction.ExportOrBuilder, com.google.protobuf.Message.Builder, com.google.protobuf.MessageLite.Builder, com.google.protobuf.MessageLiteOrBuilder, com.google.protobuf.MessageOrBuilder, Cloneable
Enclosing class:
DataProfileAction.Export
public static final class DataProfileAction.Export.Builder extends com.google.protobuf.GeneratedMessage.Builder<DataProfileAction.Export.Builder> implements DataProfileAction.ExportOrBuilder
 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

  • Method Details

    • getDescriptor

      public static final com.google.protobuf.Descriptors.Descriptor getDescriptor()

    • internalGetFieldAccessorTable

      protected com.google.protobuf.GeneratedMessage.FieldAccessorTable internalGetFieldAccessorTable()
      Specified by:
      internalGetFieldAccessorTable in class com.google.protobuf.GeneratedMessage.Builder<DataProfileAction.Export.Builder>

    • clear

      public DataProfileAction.Export.Builder clear()
      Specified by:
      clear in interface com.google.protobuf.Message.Builder
      Specified by:
      clear in interface com.google.protobuf.MessageLite.Builder
      Overrides:
      clear in class com.google.protobuf.GeneratedMessage.Builder<DataProfileAction.Export.Builder>

    • getDescriptorForType

      public com.google.protobuf.Descriptors.Descriptor getDescriptorForType()
      Specified by:
      getDescriptorForType in interface com.google.protobuf.Message.Builder
      Specified by:
      getDescriptorForType in interface com.google.protobuf.MessageOrBuilder
      Overrides:
      getDescriptorForType in class com.google.protobuf.GeneratedMessage.Builder<DataProfileAction.Export.Builder>

    • getDefaultInstanceForType

      public DataProfileAction.Export getDefaultInstanceForType()
      Specified by:
      getDefaultInstanceForType in interface com.google.protobuf.MessageLiteOrBuilder
      Specified by:
      getDefaultInstanceForType in interface com.google.protobuf.MessageOrBuilder

    • build

      public DataProfileAction.Export build()
      Specified by:
      build in interface com.google.protobuf.Message.Builder
      Specified by:
      build in interface com.google.protobuf.MessageLite.Builder

    • buildPartial

      public DataProfileAction.Export buildPartial()
      Specified by:
      buildPartial in interface com.google.protobuf.Message.Builder
      Specified by:
      buildPartial in interface com.google.protobuf.MessageLite.Builder

    • mergeFrom

      public DataProfileAction.Export.Builder mergeFrom(com.google.protobuf.Message other)
      Specified by:
      mergeFrom in interface com.google.protobuf.Message.Builder
      Overrides:
      mergeFrom in class com.google.protobuf.AbstractMessage.Builder<DataProfileAction.Export.Builder>

    • mergeFrom

      public DataProfileAction.Export.Builder mergeFrom(DataProfileAction.Export other)

    • isInitialized

      public final boolean isInitialized()
      Specified by:
      isInitialized in interface com.google.protobuf.MessageLiteOrBuilder
      Overrides:
      isInitialized in class com.google.protobuf.GeneratedMessage.Builder<DataProfileAction.Export.Builder>

    • mergeFrom

      public DataProfileAction.Export.Builder mergeFrom(com.google.protobuf.CodedInputStream input, com.google.protobuf.ExtensionRegistryLite extensionRegistry) throws IOException
      Specified by:
      mergeFrom in interface com.google.protobuf.Message.Builder
      Specified by:
      mergeFrom in interface com.google.protobuf.MessageLite.Builder
      Overrides:
      mergeFrom in class com.google.protobuf.AbstractMessage.Builder<DataProfileAction.Export.Builder>
      Throws:
      IOException

    • hasProfileTable

      public 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;
      Specified by:
      hasProfileTable in interface DataProfileAction.ExportOrBuilder
      Returns:
      Whether the profileTable field is set.

    • getProfileTable

      public 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;
      Specified by:
      getProfileTable in interface DataProfileAction.ExportOrBuilder
      Returns:
      The profileTable.

    • setProfileTable

      public DataProfileAction.Export.Builder setProfileTable(BigQueryTable value)
       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;

    • setProfileTable

      public DataProfileAction.Export.Builder setProfileTable(BigQueryTable.Builder builderForValue)
       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;

    • mergeProfileTable

      public DataProfileAction.Export.Builder mergeProfileTable(BigQueryTable value)
       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;

    • clearProfileTable

      public DataProfileAction.Export.Builder clearProfileTable()
       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;

    • getProfileTableBuilder

      public BigQueryTable.Builder getProfileTableBuilder()
       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;

    • getProfileTableOrBuilder

      public 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;
      Specified by:
      getProfileTableOrBuilder in interface DataProfileAction.ExportOrBuilder

    • hasSampleFindingsTable

      public 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;
      Specified by:
      hasSampleFindingsTable in interface DataProfileAction.ExportOrBuilder
      Returns:
      Whether the sampleFindingsTable field is set.

    • getSampleFindingsTable

      public 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;
      Specified by:
      getSampleFindingsTable in interface DataProfileAction.ExportOrBuilder
      Returns:
      The sampleFindingsTable.

    • setSampleFindingsTable

      public DataProfileAction.Export.Builder setSampleFindingsTable(BigQueryTable value)
       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;

    • setSampleFindingsTable

      public DataProfileAction.Export.Builder setSampleFindingsTable(BigQueryTable.Builder builderForValue)
       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;

    • mergeSampleFindingsTable

      public DataProfileAction.Export.Builder mergeSampleFindingsTable(BigQueryTable value)
       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;

    • clearSampleFindingsTable

      public DataProfileAction.Export.Builder clearSampleFindingsTable()
       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;

    • getSampleFindingsTableBuilder

      public BigQueryTable.Builder getSampleFindingsTableBuilder()
       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;

    • getSampleFindingsTableOrBuilder

      public 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;
      Specified by:
      getSampleFindingsTableOrBuilder in interface DataProfileAction.ExportOrBuilder