Package com.google.privacy.dlp.v2
Class Action.Deidentify.Builder
java.lang.Object
com.google.protobuf.AbstractMessageLite.Builder
com.google.protobuf.AbstractMessage.Builder<BuilderT>
com.google.protobuf.GeneratedMessage.Builder<Action.Deidentify.Builder>
com.google.privacy.dlp.v2.Action.Deidentify.Builder
- All Implemented Interfaces:
Action.DeidentifyOrBuilder,com.google.protobuf.Message.Builder,com.google.protobuf.MessageLite.Builder,com.google.protobuf.MessageLiteOrBuilder,com.google.protobuf.MessageOrBuilder,Cloneable
- Enclosing class:
- Action.Deidentify
public static final class Action.Deidentify.Builder
extends com.google.protobuf.GeneratedMessage.Builder<Action.Deidentify.Builder>
implements Action.DeidentifyOrBuilder
Create a de-identified copy of a storage bucket. Only compatible with Cloud Storage buckets. A TransformationDetail will be created for each transformation. Compatible with: Inspection of Cloud StorageProtobuf type
google.privacy.dlp.v2.Action.Deidentify-
Method Summary
Modifier and TypeMethodDescriptionaddAllFileTypesToTransform(Iterable<? extends FileType> values) List of user-specified file type groups to transform.List of user-specified file type groups to transform.addFileTypesToTransform(FileType value) List of user-specified file type groups to transform.addFileTypesToTransformValue(int value) List of user-specified file type groups to transform.build()clear()Required.List of user-specified file type groups to transform.User specified deidentify templates and configs for structured, unstructured, and image files.Config for storing transformation details.Required.com.google.protobuf.ByteStringRequired.static final com.google.protobuf.Descriptors.Descriptorcom.google.protobuf.Descriptors.DescriptorgetFileTypesToTransform(int index) List of user-specified file type groups to transform.intList of user-specified file type groups to transform.List of user-specified file type groups to transform.intgetFileTypesToTransformValue(int index) List of user-specified file type groups to transform.List of user-specified file type groups to transform.User specified deidentify templates and configs for structured, unstructured, and image files.User specified deidentify templates and configs for structured, unstructured, and image files.User specified deidentify templates and configs for structured, unstructured, and image files.Config for storing transformation details.Config for storing transformation details.Config for storing transformation details.booleanRequired.booleanUser specified deidentify templates and configs for structured, unstructured, and image files.booleanConfig for storing transformation details.protected com.google.protobuf.GeneratedMessage.FieldAccessorTablefinal booleanmergeFrom(Action.Deidentify other) mergeFrom(com.google.protobuf.CodedInputStream input, com.google.protobuf.ExtensionRegistryLite extensionRegistry) mergeFrom(com.google.protobuf.Message other) User specified deidentify templates and configs for structured, unstructured, and image files.Config for storing transformation details.setCloudStorageOutput(String value) Required.setCloudStorageOutputBytes(com.google.protobuf.ByteString value) Required.setFileTypesToTransform(int index, FileType value) List of user-specified file type groups to transform.setFileTypesToTransformValue(int index, int value) List of user-specified file type groups to transform.User specified deidentify templates and configs for structured, unstructured, and image files.setTransformationConfig(TransformationConfig.Builder builderForValue) User specified deidentify templates and configs for structured, unstructured, and image files.Config for storing transformation details.Config for storing transformation details.Methods inherited from class com.google.protobuf.GeneratedMessage.Builder
addRepeatedField, clearField, clearOneof, clone, getAllFields, getField, getFieldBuilder, getOneofFieldDescriptor, getParentForChildren, getRepeatedField, getRepeatedFieldBuilder, getRepeatedFieldCount, getUnknownFields, getUnknownFieldSetBuilder, hasField, hasOneof, internalGetMapField, internalGetMapFieldReflection, internalGetMutableMapField, internalGetMutableMapFieldReflection, isClean, markClean, mergeUnknownFields, mergeUnknownLengthDelimitedField, mergeUnknownVarintField, newBuilderForField, onBuilt, onChanged, parseUnknownField, setField, setRepeatedField, setUnknownFields, setUnknownFieldSetBuilder, setUnknownFieldsProto3Methods inherited from class com.google.protobuf.AbstractMessage.Builder
findInitializationErrors, getInitializationErrorString, internalMergeFrom, mergeFrom, mergeFrom, mergeFrom, mergeFrom, mergeFrom, mergeFrom, mergeFrom, mergeFrom, mergeFrom, newUninitializedMessageException, toStringMethods inherited from class com.google.protobuf.AbstractMessageLite.Builder
addAll, addAll, mergeDelimitedFrom, mergeDelimitedFrom, mergeFrom, newUninitializedMessageExceptionMethods inherited from class java.lang.Object
equals, finalize, getClass, hashCode, notify, notifyAll, wait, wait, waitMethods inherited from interface com.google.protobuf.Message.Builder
mergeDelimitedFrom, mergeDelimitedFromMethods inherited from interface com.google.protobuf.MessageLite.Builder
mergeFromMethods inherited from interface com.google.protobuf.MessageOrBuilder
findInitializationErrors, getAllFields, getField, getInitializationErrorString, getOneofFieldDescriptor, getRepeatedField, getRepeatedFieldCount, getUnknownFields, hasField, hasOneof
-
Method Details
-
getDescriptor
public static final com.google.protobuf.Descriptors.Descriptor getDescriptor() -
internalGetFieldAccessorTable
protected com.google.protobuf.GeneratedMessage.FieldAccessorTable internalGetFieldAccessorTable()- Specified by:
internalGetFieldAccessorTablein classcom.google.protobuf.GeneratedMessage.Builder<Action.Deidentify.Builder>
-
clear
- Specified by:
clearin interfacecom.google.protobuf.Message.Builder- Specified by:
clearin interfacecom.google.protobuf.MessageLite.Builder- Overrides:
clearin classcom.google.protobuf.GeneratedMessage.Builder<Action.Deidentify.Builder>
-
getDescriptorForType
public com.google.protobuf.Descriptors.Descriptor getDescriptorForType()- Specified by:
getDescriptorForTypein interfacecom.google.protobuf.Message.Builder- Specified by:
getDescriptorForTypein interfacecom.google.protobuf.MessageOrBuilder- Overrides:
getDescriptorForTypein classcom.google.protobuf.GeneratedMessage.Builder<Action.Deidentify.Builder>
-
getDefaultInstanceForType
- Specified by:
getDefaultInstanceForTypein interfacecom.google.protobuf.MessageLiteOrBuilder- Specified by:
getDefaultInstanceForTypein interfacecom.google.protobuf.MessageOrBuilder
-
build
- Specified by:
buildin interfacecom.google.protobuf.Message.Builder- Specified by:
buildin interfacecom.google.protobuf.MessageLite.Builder
-
buildPartial
- Specified by:
buildPartialin interfacecom.google.protobuf.Message.Builder- Specified by:
buildPartialin interfacecom.google.protobuf.MessageLite.Builder
-
mergeFrom
- Specified by:
mergeFromin interfacecom.google.protobuf.Message.Builder- Overrides:
mergeFromin classcom.google.protobuf.AbstractMessage.Builder<Action.Deidentify.Builder>
-
mergeFrom
-
isInitialized
public final boolean isInitialized()- Specified by:
isInitializedin interfacecom.google.protobuf.MessageLiteOrBuilder- Overrides:
isInitializedin classcom.google.protobuf.GeneratedMessage.Builder<Action.Deidentify.Builder>
-
mergeFrom
public Action.Deidentify.Builder mergeFrom(com.google.protobuf.CodedInputStream input, com.google.protobuf.ExtensionRegistryLite extensionRegistry) throws IOException - Specified by:
mergeFromin interfacecom.google.protobuf.Message.Builder- Specified by:
mergeFromin interfacecom.google.protobuf.MessageLite.Builder- Overrides:
mergeFromin classcom.google.protobuf.AbstractMessage.Builder<Action.Deidentify.Builder>- Throws:
IOException
-
getOutputCase
- Specified by:
getOutputCasein interfaceAction.DeidentifyOrBuilder
-
clearOutput
-
hasTransformationConfig
public boolean hasTransformationConfig()User specified deidentify templates and configs for structured, unstructured, and image files.
.google.privacy.dlp.v2.TransformationConfig transformation_config = 7;- Specified by:
hasTransformationConfigin interfaceAction.DeidentifyOrBuilder- Returns:
- Whether the transformationConfig field is set.
-
getTransformationConfig
User specified deidentify templates and configs for structured, unstructured, and image files.
.google.privacy.dlp.v2.TransformationConfig transformation_config = 7;- Specified by:
getTransformationConfigin interfaceAction.DeidentifyOrBuilder- Returns:
- The transformationConfig.
-
setTransformationConfig
User specified deidentify templates and configs for structured, unstructured, and image files.
.google.privacy.dlp.v2.TransformationConfig transformation_config = 7; -
setTransformationConfig
public Action.Deidentify.Builder setTransformationConfig(TransformationConfig.Builder builderForValue) User specified deidentify templates and configs for structured, unstructured, and image files.
.google.privacy.dlp.v2.TransformationConfig transformation_config = 7; -
mergeTransformationConfig
User specified deidentify templates and configs for structured, unstructured, and image files.
.google.privacy.dlp.v2.TransformationConfig transformation_config = 7; -
clearTransformationConfig
User specified deidentify templates and configs for structured, unstructured, and image files.
.google.privacy.dlp.v2.TransformationConfig transformation_config = 7; -
getTransformationConfigBuilder
User specified deidentify templates and configs for structured, unstructured, and image files.
.google.privacy.dlp.v2.TransformationConfig transformation_config = 7; -
getTransformationConfigOrBuilder
User specified deidentify templates and configs for structured, unstructured, and image files.
.google.privacy.dlp.v2.TransformationConfig transformation_config = 7;- Specified by:
getTransformationConfigOrBuilderin interfaceAction.DeidentifyOrBuilder
-
hasTransformationDetailsStorageConfig
public boolean hasTransformationDetailsStorageConfig()Config for storing transformation details. This field specifies the configuration for storing detailed metadata about each transformation performed during a de-identification process. The metadata is stored separately from the de-identified content itself and provides a granular record of both successful transformations and any failures that occurred. Enabling this configuration is essential for users who need to access comprehensive information about the status, outcome, and specifics of each transformation. The details are captured in the [TransformationDetails][google.privacy.dlp.v2.TransformationDetails] message for each operation. Key use cases: * **Auditing and compliance** * Provides a verifiable audit trail of de-identification activities, which is crucial for meeting regulatory requirements and internal data governance policies. * Logs what data was transformed, what transformations were applied, when they occurred, and their success status. This helps demonstrate accountability and due diligence in protecting sensitive data. * **Troubleshooting and debugging** * Offers detailed error messages and context if a transformation fails. This information is useful for diagnosing and resolving issues in the de-identification pipeline. * Helps pinpoint the exact location and nature of failures, speeding up the debugging process. * **Process verification and quality assurance** * Allows users to confirm that de-identification rules and transformations were applied correctly and consistently across the dataset as intended. * Helps in verifying the effectiveness of the chosen de-identification strategies. * **Data lineage and impact analysis** * Creates a record of how data elements were modified, contributing to data lineage. This is useful for understanding the provenance of de-identified data. * Aids in assessing the potential impact of de-identification choices on downstream analytical processes or data usability. * **Reporting and operational insights** * You can analyze the metadata stored in a queryable BigQuery table to generate reports on transformation success rates, common error types, processing volumes (e.g., transformedBytes), and the types of transformations applied. * These insights can inform optimization of de-identification configurations and resource planning. To take advantage of these benefits, set this configuration. The stored details include a description of the transformation, success or error codes, error messages, the number of bytes transformed, the location of the transformed content, and identifiers for the job and source data.
.google.privacy.dlp.v2.TransformationDetailsStorageConfig transformation_details_storage_config = 3;- Specified by:
hasTransformationDetailsStorageConfigin interfaceAction.DeidentifyOrBuilder- Returns:
- Whether the transformationDetailsStorageConfig field is set.
-
getTransformationDetailsStorageConfig
Config for storing transformation details. This field specifies the configuration for storing detailed metadata about each transformation performed during a de-identification process. The metadata is stored separately from the de-identified content itself and provides a granular record of both successful transformations and any failures that occurred. Enabling this configuration is essential for users who need to access comprehensive information about the status, outcome, and specifics of each transformation. The details are captured in the [TransformationDetails][google.privacy.dlp.v2.TransformationDetails] message for each operation. Key use cases: * **Auditing and compliance** * Provides a verifiable audit trail of de-identification activities, which is crucial for meeting regulatory requirements and internal data governance policies. * Logs what data was transformed, what transformations were applied, when they occurred, and their success status. This helps demonstrate accountability and due diligence in protecting sensitive data. * **Troubleshooting and debugging** * Offers detailed error messages and context if a transformation fails. This information is useful for diagnosing and resolving issues in the de-identification pipeline. * Helps pinpoint the exact location and nature of failures, speeding up the debugging process. * **Process verification and quality assurance** * Allows users to confirm that de-identification rules and transformations were applied correctly and consistently across the dataset as intended. * Helps in verifying the effectiveness of the chosen de-identification strategies. * **Data lineage and impact analysis** * Creates a record of how data elements were modified, contributing to data lineage. This is useful for understanding the provenance of de-identified data. * Aids in assessing the potential impact of de-identification choices on downstream analytical processes or data usability. * **Reporting and operational insights** * You can analyze the metadata stored in a queryable BigQuery table to generate reports on transformation success rates, common error types, processing volumes (e.g., transformedBytes), and the types of transformations applied. * These insights can inform optimization of de-identification configurations and resource planning. To take advantage of these benefits, set this configuration. The stored details include a description of the transformation, success or error codes, error messages, the number of bytes transformed, the location of the transformed content, and identifiers for the job and source data.
.google.privacy.dlp.v2.TransformationDetailsStorageConfig transformation_details_storage_config = 3;- Specified by:
getTransformationDetailsStorageConfigin interfaceAction.DeidentifyOrBuilder- Returns:
- The transformationDetailsStorageConfig.
-
setTransformationDetailsStorageConfig
public Action.Deidentify.Builder setTransformationDetailsStorageConfig(TransformationDetailsStorageConfig value) Config for storing transformation details. This field specifies the configuration for storing detailed metadata about each transformation performed during a de-identification process. The metadata is stored separately from the de-identified content itself and provides a granular record of both successful transformations and any failures that occurred. Enabling this configuration is essential for users who need to access comprehensive information about the status, outcome, and specifics of each transformation. The details are captured in the [TransformationDetails][google.privacy.dlp.v2.TransformationDetails] message for each operation. Key use cases: * **Auditing and compliance** * Provides a verifiable audit trail of de-identification activities, which is crucial for meeting regulatory requirements and internal data governance policies. * Logs what data was transformed, what transformations were applied, when they occurred, and their success status. This helps demonstrate accountability and due diligence in protecting sensitive data. * **Troubleshooting and debugging** * Offers detailed error messages and context if a transformation fails. This information is useful for diagnosing and resolving issues in the de-identification pipeline. * Helps pinpoint the exact location and nature of failures, speeding up the debugging process. * **Process verification and quality assurance** * Allows users to confirm that de-identification rules and transformations were applied correctly and consistently across the dataset as intended. * Helps in verifying the effectiveness of the chosen de-identification strategies. * **Data lineage and impact analysis** * Creates a record of how data elements were modified, contributing to data lineage. This is useful for understanding the provenance of de-identified data. * Aids in assessing the potential impact of de-identification choices on downstream analytical processes or data usability. * **Reporting and operational insights** * You can analyze the metadata stored in a queryable BigQuery table to generate reports on transformation success rates, common error types, processing volumes (e.g., transformedBytes), and the types of transformations applied. * These insights can inform optimization of de-identification configurations and resource planning. To take advantage of these benefits, set this configuration. The stored details include a description of the transformation, success or error codes, error messages, the number of bytes transformed, the location of the transformed content, and identifiers for the job and source data.
.google.privacy.dlp.v2.TransformationDetailsStorageConfig transformation_details_storage_config = 3; -
setTransformationDetailsStorageConfig
public Action.Deidentify.Builder setTransformationDetailsStorageConfig(TransformationDetailsStorageConfig.Builder builderForValue) Config for storing transformation details. This field specifies the configuration for storing detailed metadata about each transformation performed during a de-identification process. The metadata is stored separately from the de-identified content itself and provides a granular record of both successful transformations and any failures that occurred. Enabling this configuration is essential for users who need to access comprehensive information about the status, outcome, and specifics of each transformation. The details are captured in the [TransformationDetails][google.privacy.dlp.v2.TransformationDetails] message for each operation. Key use cases: * **Auditing and compliance** * Provides a verifiable audit trail of de-identification activities, which is crucial for meeting regulatory requirements and internal data governance policies. * Logs what data was transformed, what transformations were applied, when they occurred, and their success status. This helps demonstrate accountability and due diligence in protecting sensitive data. * **Troubleshooting and debugging** * Offers detailed error messages and context if a transformation fails. This information is useful for diagnosing and resolving issues in the de-identification pipeline. * Helps pinpoint the exact location and nature of failures, speeding up the debugging process. * **Process verification and quality assurance** * Allows users to confirm that de-identification rules and transformations were applied correctly and consistently across the dataset as intended. * Helps in verifying the effectiveness of the chosen de-identification strategies. * **Data lineage and impact analysis** * Creates a record of how data elements were modified, contributing to data lineage. This is useful for understanding the provenance of de-identified data. * Aids in assessing the potential impact of de-identification choices on downstream analytical processes or data usability. * **Reporting and operational insights** * You can analyze the metadata stored in a queryable BigQuery table to generate reports on transformation success rates, common error types, processing volumes (e.g., transformedBytes), and the types of transformations applied. * These insights can inform optimization of de-identification configurations and resource planning. To take advantage of these benefits, set this configuration. The stored details include a description of the transformation, success or error codes, error messages, the number of bytes transformed, the location of the transformed content, and identifiers for the job and source data.
.google.privacy.dlp.v2.TransformationDetailsStorageConfig transformation_details_storage_config = 3; -
mergeTransformationDetailsStorageConfig
public Action.Deidentify.Builder mergeTransformationDetailsStorageConfig(TransformationDetailsStorageConfig value) Config for storing transformation details. This field specifies the configuration for storing detailed metadata about each transformation performed during a de-identification process. The metadata is stored separately from the de-identified content itself and provides a granular record of both successful transformations and any failures that occurred. Enabling this configuration is essential for users who need to access comprehensive information about the status, outcome, and specifics of each transformation. The details are captured in the [TransformationDetails][google.privacy.dlp.v2.TransformationDetails] message for each operation. Key use cases: * **Auditing and compliance** * Provides a verifiable audit trail of de-identification activities, which is crucial for meeting regulatory requirements and internal data governance policies. * Logs what data was transformed, what transformations were applied, when they occurred, and their success status. This helps demonstrate accountability and due diligence in protecting sensitive data. * **Troubleshooting and debugging** * Offers detailed error messages and context if a transformation fails. This information is useful for diagnosing and resolving issues in the de-identification pipeline. * Helps pinpoint the exact location and nature of failures, speeding up the debugging process. * **Process verification and quality assurance** * Allows users to confirm that de-identification rules and transformations were applied correctly and consistently across the dataset as intended. * Helps in verifying the effectiveness of the chosen de-identification strategies. * **Data lineage and impact analysis** * Creates a record of how data elements were modified, contributing to data lineage. This is useful for understanding the provenance of de-identified data. * Aids in assessing the potential impact of de-identification choices on downstream analytical processes or data usability. * **Reporting and operational insights** * You can analyze the metadata stored in a queryable BigQuery table to generate reports on transformation success rates, common error types, processing volumes (e.g., transformedBytes), and the types of transformations applied. * These insights can inform optimization of de-identification configurations and resource planning. To take advantage of these benefits, set this configuration. The stored details include a description of the transformation, success or error codes, error messages, the number of bytes transformed, the location of the transformed content, and identifiers for the job and source data.
.google.privacy.dlp.v2.TransformationDetailsStorageConfig transformation_details_storage_config = 3; -
clearTransformationDetailsStorageConfig
Config for storing transformation details. This field specifies the configuration for storing detailed metadata about each transformation performed during a de-identification process. The metadata is stored separately from the de-identified content itself and provides a granular record of both successful transformations and any failures that occurred. Enabling this configuration is essential for users who need to access comprehensive information about the status, outcome, and specifics of each transformation. The details are captured in the [TransformationDetails][google.privacy.dlp.v2.TransformationDetails] message for each operation. Key use cases: * **Auditing and compliance** * Provides a verifiable audit trail of de-identification activities, which is crucial for meeting regulatory requirements and internal data governance policies. * Logs what data was transformed, what transformations were applied, when they occurred, and their success status. This helps demonstrate accountability and due diligence in protecting sensitive data. * **Troubleshooting and debugging** * Offers detailed error messages and context if a transformation fails. This information is useful for diagnosing and resolving issues in the de-identification pipeline. * Helps pinpoint the exact location and nature of failures, speeding up the debugging process. * **Process verification and quality assurance** * Allows users to confirm that de-identification rules and transformations were applied correctly and consistently across the dataset as intended. * Helps in verifying the effectiveness of the chosen de-identification strategies. * **Data lineage and impact analysis** * Creates a record of how data elements were modified, contributing to data lineage. This is useful for understanding the provenance of de-identified data. * Aids in assessing the potential impact of de-identification choices on downstream analytical processes or data usability. * **Reporting and operational insights** * You can analyze the metadata stored in a queryable BigQuery table to generate reports on transformation success rates, common error types, processing volumes (e.g., transformedBytes), and the types of transformations applied. * These insights can inform optimization of de-identification configurations and resource planning. To take advantage of these benefits, set this configuration. The stored details include a description of the transformation, success or error codes, error messages, the number of bytes transformed, the location of the transformed content, and identifiers for the job and source data.
.google.privacy.dlp.v2.TransformationDetailsStorageConfig transformation_details_storage_config = 3; -
getTransformationDetailsStorageConfigBuilder
Config for storing transformation details. This field specifies the configuration for storing detailed metadata about each transformation performed during a de-identification process. The metadata is stored separately from the de-identified content itself and provides a granular record of both successful transformations and any failures that occurred. Enabling this configuration is essential for users who need to access comprehensive information about the status, outcome, and specifics of each transformation. The details are captured in the [TransformationDetails][google.privacy.dlp.v2.TransformationDetails] message for each operation. Key use cases: * **Auditing and compliance** * Provides a verifiable audit trail of de-identification activities, which is crucial for meeting regulatory requirements and internal data governance policies. * Logs what data was transformed, what transformations were applied, when they occurred, and their success status. This helps demonstrate accountability and due diligence in protecting sensitive data. * **Troubleshooting and debugging** * Offers detailed error messages and context if a transformation fails. This information is useful for diagnosing and resolving issues in the de-identification pipeline. * Helps pinpoint the exact location and nature of failures, speeding up the debugging process. * **Process verification and quality assurance** * Allows users to confirm that de-identification rules and transformations were applied correctly and consistently across the dataset as intended. * Helps in verifying the effectiveness of the chosen de-identification strategies. * **Data lineage and impact analysis** * Creates a record of how data elements were modified, contributing to data lineage. This is useful for understanding the provenance of de-identified data. * Aids in assessing the potential impact of de-identification choices on downstream analytical processes or data usability. * **Reporting and operational insights** * You can analyze the metadata stored in a queryable BigQuery table to generate reports on transformation success rates, common error types, processing volumes (e.g., transformedBytes), and the types of transformations applied. * These insights can inform optimization of de-identification configurations and resource planning. To take advantage of these benefits, set this configuration. The stored details include a description of the transformation, success or error codes, error messages, the number of bytes transformed, the location of the transformed content, and identifiers for the job and source data.
.google.privacy.dlp.v2.TransformationDetailsStorageConfig transformation_details_storage_config = 3; -
getTransformationDetailsStorageConfigOrBuilder
Config for storing transformation details. This field specifies the configuration for storing detailed metadata about each transformation performed during a de-identification process. The metadata is stored separately from the de-identified content itself and provides a granular record of both successful transformations and any failures that occurred. Enabling this configuration is essential for users who need to access comprehensive information about the status, outcome, and specifics of each transformation. The details are captured in the [TransformationDetails][google.privacy.dlp.v2.TransformationDetails] message for each operation. Key use cases: * **Auditing and compliance** * Provides a verifiable audit trail of de-identification activities, which is crucial for meeting regulatory requirements and internal data governance policies. * Logs what data was transformed, what transformations were applied, when they occurred, and their success status. This helps demonstrate accountability and due diligence in protecting sensitive data. * **Troubleshooting and debugging** * Offers detailed error messages and context if a transformation fails. This information is useful for diagnosing and resolving issues in the de-identification pipeline. * Helps pinpoint the exact location and nature of failures, speeding up the debugging process. * **Process verification and quality assurance** * Allows users to confirm that de-identification rules and transformations were applied correctly and consistently across the dataset as intended. * Helps in verifying the effectiveness of the chosen de-identification strategies. * **Data lineage and impact analysis** * Creates a record of how data elements were modified, contributing to data lineage. This is useful for understanding the provenance of de-identified data. * Aids in assessing the potential impact of de-identification choices on downstream analytical processes or data usability. * **Reporting and operational insights** * You can analyze the metadata stored in a queryable BigQuery table to generate reports on transformation success rates, common error types, processing volumes (e.g., transformedBytes), and the types of transformations applied. * These insights can inform optimization of de-identification configurations and resource planning. To take advantage of these benefits, set this configuration. The stored details include a description of the transformation, success or error codes, error messages, the number of bytes transformed, the location of the transformed content, and identifiers for the job and source data.
.google.privacy.dlp.v2.TransformationDetailsStorageConfig transformation_details_storage_config = 3;- Specified by:
getTransformationDetailsStorageConfigOrBuilderin interfaceAction.DeidentifyOrBuilder
-
hasCloudStorageOutput
public boolean hasCloudStorageOutput()Required. User settable Cloud Storage bucket and folders to store de-identified files. This field must be set for Cloud Storage deidentification. The output Cloud Storage bucket must be different from the input bucket. De-identified files will overwrite files in the output path. Form of: gs://bucket/folder/ or gs://bucket
string cloud_storage_output = 9 [(.google.api.field_behavior) = REQUIRED];- Specified by:
hasCloudStorageOutputin interfaceAction.DeidentifyOrBuilder- Returns:
- Whether the cloudStorageOutput field is set.
-
getCloudStorageOutput
Required. User settable Cloud Storage bucket and folders to store de-identified files. This field must be set for Cloud Storage deidentification. The output Cloud Storage bucket must be different from the input bucket. De-identified files will overwrite files in the output path. Form of: gs://bucket/folder/ or gs://bucket
string cloud_storage_output = 9 [(.google.api.field_behavior) = REQUIRED];- Specified by:
getCloudStorageOutputin interfaceAction.DeidentifyOrBuilder- Returns:
- The cloudStorageOutput.
-
getCloudStorageOutputBytes
public com.google.protobuf.ByteString getCloudStorageOutputBytes()Required. User settable Cloud Storage bucket and folders to store de-identified files. This field must be set for Cloud Storage deidentification. The output Cloud Storage bucket must be different from the input bucket. De-identified files will overwrite files in the output path. Form of: gs://bucket/folder/ or gs://bucket
string cloud_storage_output = 9 [(.google.api.field_behavior) = REQUIRED];- Specified by:
getCloudStorageOutputBytesin interfaceAction.DeidentifyOrBuilder- Returns:
- The bytes for cloudStorageOutput.
-
setCloudStorageOutput
Required. User settable Cloud Storage bucket and folders to store de-identified files. This field must be set for Cloud Storage deidentification. The output Cloud Storage bucket must be different from the input bucket. De-identified files will overwrite files in the output path. Form of: gs://bucket/folder/ or gs://bucket
string cloud_storage_output = 9 [(.google.api.field_behavior) = REQUIRED];- Parameters:
value- The cloudStorageOutput to set.- Returns:
- This builder for chaining.
-
clearCloudStorageOutput
Required. User settable Cloud Storage bucket and folders to store de-identified files. This field must be set for Cloud Storage deidentification. The output Cloud Storage bucket must be different from the input bucket. De-identified files will overwrite files in the output path. Form of: gs://bucket/folder/ or gs://bucket
string cloud_storage_output = 9 [(.google.api.field_behavior) = REQUIRED];- Returns:
- This builder for chaining.
-
setCloudStorageOutputBytes
Required. User settable Cloud Storage bucket and folders to store de-identified files. This field must be set for Cloud Storage deidentification. The output Cloud Storage bucket must be different from the input bucket. De-identified files will overwrite files in the output path. Form of: gs://bucket/folder/ or gs://bucket
string cloud_storage_output = 9 [(.google.api.field_behavior) = REQUIRED];- Parameters:
value- The bytes for cloudStorageOutput to set.- Returns:
- This builder for chaining.
-
getFileTypesToTransformList
List of user-specified file type groups to transform. If specified, only the files with these file types are transformed. If empty, all supported files are transformed. Supported types may be automatically added over time. Any unsupported file types that are set in this field are excluded from de-identification. An error is recorded for each unsupported file in the TransformationDetails output table. Currently the only file types supported are: IMAGES, TEXT_FILES, CSV, TSV.
repeated .google.privacy.dlp.v2.FileType file_types_to_transform = 8;- Specified by:
getFileTypesToTransformListin interfaceAction.DeidentifyOrBuilder- Returns:
- A list containing the fileTypesToTransform.
-
getFileTypesToTransformCount
public int getFileTypesToTransformCount()List of user-specified file type groups to transform. If specified, only the files with these file types are transformed. If empty, all supported files are transformed. Supported types may be automatically added over time. Any unsupported file types that are set in this field are excluded from de-identification. An error is recorded for each unsupported file in the TransformationDetails output table. Currently the only file types supported are: IMAGES, TEXT_FILES, CSV, TSV.
repeated .google.privacy.dlp.v2.FileType file_types_to_transform = 8;- Specified by:
getFileTypesToTransformCountin interfaceAction.DeidentifyOrBuilder- Returns:
- The count of fileTypesToTransform.
-
getFileTypesToTransform
List of user-specified file type groups to transform. If specified, only the files with these file types are transformed. If empty, all supported files are transformed. Supported types may be automatically added over time. Any unsupported file types that are set in this field are excluded from de-identification. An error is recorded for each unsupported file in the TransformationDetails output table. Currently the only file types supported are: IMAGES, TEXT_FILES, CSV, TSV.
repeated .google.privacy.dlp.v2.FileType file_types_to_transform = 8;- Specified by:
getFileTypesToTransformin interfaceAction.DeidentifyOrBuilder- Parameters:
index- The index of the element to return.- Returns:
- The fileTypesToTransform at the given index.
-
setFileTypesToTransform
List of user-specified file type groups to transform. If specified, only the files with these file types are transformed. If empty, all supported files are transformed. Supported types may be automatically added over time. Any unsupported file types that are set in this field are excluded from de-identification. An error is recorded for each unsupported file in the TransformationDetails output table. Currently the only file types supported are: IMAGES, TEXT_FILES, CSV, TSV.
repeated .google.privacy.dlp.v2.FileType file_types_to_transform = 8;- Parameters:
index- The index to set the value at.value- The fileTypesToTransform to set.- Returns:
- This builder for chaining.
-
addFileTypesToTransform
List of user-specified file type groups to transform. If specified, only the files with these file types are transformed. If empty, all supported files are transformed. Supported types may be automatically added over time. Any unsupported file types that are set in this field are excluded from de-identification. An error is recorded for each unsupported file in the TransformationDetails output table. Currently the only file types supported are: IMAGES, TEXT_FILES, CSV, TSV.
repeated .google.privacy.dlp.v2.FileType file_types_to_transform = 8;- Parameters:
value- The fileTypesToTransform to add.- Returns:
- This builder for chaining.
-
addAllFileTypesToTransform
List of user-specified file type groups to transform. If specified, only the files with these file types are transformed. If empty, all supported files are transformed. Supported types may be automatically added over time. Any unsupported file types that are set in this field are excluded from de-identification. An error is recorded for each unsupported file in the TransformationDetails output table. Currently the only file types supported are: IMAGES, TEXT_FILES, CSV, TSV.
repeated .google.privacy.dlp.v2.FileType file_types_to_transform = 8;- Parameters:
values- The fileTypesToTransform to add.- Returns:
- This builder for chaining.
-
clearFileTypesToTransform
List of user-specified file type groups to transform. If specified, only the files with these file types are transformed. If empty, all supported files are transformed. Supported types may be automatically added over time. Any unsupported file types that are set in this field are excluded from de-identification. An error is recorded for each unsupported file in the TransformationDetails output table. Currently the only file types supported are: IMAGES, TEXT_FILES, CSV, TSV.
repeated .google.privacy.dlp.v2.FileType file_types_to_transform = 8;- Returns:
- This builder for chaining.
-
getFileTypesToTransformValueList
List of user-specified file type groups to transform. If specified, only the files with these file types are transformed. If empty, all supported files are transformed. Supported types may be automatically added over time. Any unsupported file types that are set in this field are excluded from de-identification. An error is recorded for each unsupported file in the TransformationDetails output table. Currently the only file types supported are: IMAGES, TEXT_FILES, CSV, TSV.
repeated .google.privacy.dlp.v2.FileType file_types_to_transform = 8;- Specified by:
getFileTypesToTransformValueListin interfaceAction.DeidentifyOrBuilder- Returns:
- A list containing the enum numeric values on the wire for fileTypesToTransform.
-
getFileTypesToTransformValue
public int getFileTypesToTransformValue(int index) List of user-specified file type groups to transform. If specified, only the files with these file types are transformed. If empty, all supported files are transformed. Supported types may be automatically added over time. Any unsupported file types that are set in this field are excluded from de-identification. An error is recorded for each unsupported file in the TransformationDetails output table. Currently the only file types supported are: IMAGES, TEXT_FILES, CSV, TSV.
repeated .google.privacy.dlp.v2.FileType file_types_to_transform = 8;- Specified by:
getFileTypesToTransformValuein interfaceAction.DeidentifyOrBuilder- Parameters:
index- The index of the value to return.- Returns:
- The enum numeric value on the wire of fileTypesToTransform at the given index.
-
setFileTypesToTransformValue
List of user-specified file type groups to transform. If specified, only the files with these file types are transformed. If empty, all supported files are transformed. Supported types may be automatically added over time. Any unsupported file types that are set in this field are excluded from de-identification. An error is recorded for each unsupported file in the TransformationDetails output table. Currently the only file types supported are: IMAGES, TEXT_FILES, CSV, TSV.
repeated .google.privacy.dlp.v2.FileType file_types_to_transform = 8;- Parameters:
index- The index to set the value at.value- The enum numeric value on the wire for fileTypesToTransform to set.- Returns:
- This builder for chaining.
-
addFileTypesToTransformValue
List of user-specified file type groups to transform. If specified, only the files with these file types are transformed. If empty, all supported files are transformed. Supported types may be automatically added over time. Any unsupported file types that are set in this field are excluded from de-identification. An error is recorded for each unsupported file in the TransformationDetails output table. Currently the only file types supported are: IMAGES, TEXT_FILES, CSV, TSV.
repeated .google.privacy.dlp.v2.FileType file_types_to_transform = 8;- Parameters:
value- The enum numeric value on the wire for fileTypesToTransform to add.- Returns:
- This builder for chaining.
-
addAllFileTypesToTransformValue
List of user-specified file type groups to transform. If specified, only the files with these file types are transformed. If empty, all supported files are transformed. Supported types may be automatically added over time. Any unsupported file types that are set in this field are excluded from de-identification. An error is recorded for each unsupported file in the TransformationDetails output table. Currently the only file types supported are: IMAGES, TEXT_FILES, CSV, TSV.
repeated .google.privacy.dlp.v2.FileType file_types_to_transform = 8;- Parameters:
values- The enum numeric values on the wire for fileTypesToTransform to add.- Returns:
- This builder for chaining.
-