Cloud Data Loss Prevention (DLP) V2 API - Class Google::Cloud::Dlp::V2::DataProfileAction::Export (v1.1.0)

Reference documentation and code samples for the Cloud Data Loss Prevention (DLP) V2 API class Google::Cloud::Dlp::V2::DataProfileAction::Export.

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

Inherits

  • Object

Extended By

  • Google::Protobuf::MessageExts::ClassMethods

Includes

  • Google::Protobuf::MessageExts

Methods

#profile_table

def profile_table() -> ::Google::Cloud::Dlp::V2::BigQueryTable
Returns
  • (::Google::Cloud::Dlp::V2::BigQueryTable) — Store all table and column profiles in an existing table or a new table in an existing dataset. Each re-generation will result in new rows in BigQuery. 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.

#profile_table=

def profile_table=(value) -> ::Google::Cloud::Dlp::V2::BigQueryTable
Parameter
  • value (::Google::Cloud::Dlp::V2::BigQueryTable) — Store all table and column profiles in an existing table or a new table in an existing dataset. Each re-generation will result in new rows in BigQuery. 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.
Returns
  • (::Google::Cloud::Dlp::V2::BigQueryTable) — Store all table and column profiles in an existing table or a new table in an existing dataset. Each re-generation will result in new rows in BigQuery. 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.