Package com.google.privacy.dlp.v2

Interface OutputStorageConfigOrBuilder

  • All Superinterfaces:
    com.google.protobuf.MessageLiteOrBuilder, com.google.protobuf.MessageOrBuilder
    All Known Implementing Classes:
    OutputStorageConfig, OutputStorageConfig.Builder
    public interface OutputStorageConfigOrBuilder
extends com.google.protobuf.MessageOrBuilder

    • Method Detail

      • hasTable

        boolean hasTable()
         Store findings in an existing table or a new table in an existing
 dataset. If table_id is not set a new one will be generated
 for you with the following format:
 dlp_googleapis_yyyy_mm_dd_[dlp_job_id]. Pacific time zone will be used
 for generating the date details.

 For Inspect, each column in an existing output table must have the same
 name, type, and mode of a field in the `Finding` object.

 For Risk, an existing output table should be the output of a previous
 Risk analysis job run on the same source table, with the same privacy
 metric and quasi-identifiers. Risk jobs that analyze the same table but
 compute a different privacy metric, or use different sets of
 quasi-identifiers, cannot store their results in the same table.
        .google.privacy.dlp.v2.BigQueryTable table = 1;
        Returns:
        Whether the table field is set.

      • getTable

        BigQueryTable getTable()
         Store findings in an existing table or a new table in an existing
 dataset. If table_id is not set a new one will be generated
 for you with the following format:
 dlp_googleapis_yyyy_mm_dd_[dlp_job_id]. Pacific time zone will be used
 for generating the date details.

 For Inspect, each column in an existing output table must have the same
 name, type, and mode of a field in the `Finding` object.

 For Risk, an existing output table should be the output of a previous
 Risk analysis job run on the same source table, with the same privacy
 metric and quasi-identifiers. Risk jobs that analyze the same table but
 compute a different privacy metric, or use different sets of
 quasi-identifiers, cannot store their results in the same table.
        .google.privacy.dlp.v2.BigQueryTable table = 1;
        Returns:
        The table.

      • getTableOrBuilder

        BigQueryTableOrBuilder getTableOrBuilder()
         Store findings in an existing table or a new table in an existing
 dataset. If table_id is not set a new one will be generated
 for you with the following format:
 dlp_googleapis_yyyy_mm_dd_[dlp_job_id]. Pacific time zone will be used
 for generating the date details.

 For Inspect, each column in an existing output table must have the same
 name, type, and mode of a field in the `Finding` object.

 For Risk, an existing output table should be the output of a previous
 Risk analysis job run on the same source table, with the same privacy
 metric and quasi-identifiers. Risk jobs that analyze the same table but
 compute a different privacy metric, or use different sets of
 quasi-identifiers, cannot store their results in the same table.
        .google.privacy.dlp.v2.BigQueryTable table = 1;

      • getOutputSchemaValue

        int getOutputSchemaValue()
         Schema used for writing the findings for Inspect jobs. This field is only
 used for Inspect and must be unspecified for Risk jobs. Columns are derived
 from the `Finding` object. If appending to an existing table, any columns
 from the predefined schema that are missing will be added. No columns in
 the existing table will be deleted.

 If unspecified, then all available columns will be used for a new table or
 an (existing) table with no schema, and no changes will be made to an
 existing table that has a schema.
 Only for use with external storage.
        .google.privacy.dlp.v2.OutputStorageConfig.OutputSchema output_schema = 3;
        Returns:
        The enum numeric value on the wire for outputSchema.

      • getOutputSchema

        OutputStorageConfig.OutputSchema getOutputSchema()
         Schema used for writing the findings for Inspect jobs. This field is only
 used for Inspect and must be unspecified for Risk jobs. Columns are derived
 from the `Finding` object. If appending to an existing table, any columns
 from the predefined schema that are missing will be added. No columns in
 the existing table will be deleted.

 If unspecified, then all available columns will be used for a new table or
 an (existing) table with no schema, and no changes will be made to an
 existing table that has a schema.
 Only for use with external storage.
        .google.privacy.dlp.v2.OutputStorageConfig.OutputSchema output_schema = 3;
        Returns:
        The outputSchema.