- 3.87.0 (latest)
- 3.86.0
- 3.85.0
- 3.84.0
- 3.82.0
- 3.80.0
- 3.79.0
- 3.78.0
- 3.77.0
- 3.76.0
- 3.74.0
- 3.72.0
- 3.71.0
- 3.68.0
- 3.67.0
- 3.66.0
- 3.64.0
- 3.63.0
- 3.62.0
- 3.61.0
- 3.60.0
- 3.59.0
- 3.58.0
- 3.57.0
- 3.56.0
- 3.55.0
- 3.53.0
- 3.52.0
- 3.51.0
- 3.50.0
- 3.49.0
- 3.48.0
- 3.47.0
- 3.46.0
- 3.45.0
- 3.44.0
- 3.43.0
- 3.41.0
- 3.40.0
- 3.39.0
- 3.38.0
- 3.37.0
- 3.36.0
- 3.35.0
- 3.34.0
- 3.33.0
- 3.32.0
- 3.31.0
- 3.28.0
- 3.27.0
- 3.26.0
- 3.25.0
- 3.24.0
- 3.23.0
- 3.22.0
- 3.21.0
- 3.20.0
- 3.19.0
- 3.18.0
- 3.17.0
- 3.16.0
- 3.15.0
- 3.13.0
- 3.12.0
- 3.11.0
- 3.10.0
- 3.9.0
- 3.8.0
- 3.7.6
- 3.6.7
- 3.5.0
- 3.4.0
- 3.3.2
- 3.2.1
- 3.1.4
public static final class DataProfileAction.Export.Builder extends GeneratedMessage.Builder<DataProfileAction.Export.Builder> implements DataProfileAction.ExportOrBuilderIf set, the detailed data profiles will be persisted to the location of your choice whenever updated.
Protobuf type google.privacy.dlp.v2.DataProfileAction.Export
Inheritance
java.lang.Object > AbstractMessageLite.Builder<MessageType,BuilderType> > AbstractMessage.Builder<BuilderType> > GeneratedMessage.Builder > DataProfileAction.Export.BuilderImplements
DataProfileAction.ExportOrBuilderStatic Methods
getDescriptor()
public static final Descriptors.Descriptor getDescriptor()| Returns | |
|---|---|
| Type | Description |
Descriptor |
|
Methods
build()
public DataProfileAction.Export build()| Returns | |
|---|---|
| Type | Description |
DataProfileAction.Export |
|
buildPartial()
public DataProfileAction.Export buildPartial()| Returns | |
|---|---|
| Type | Description |
DataProfileAction.Export |
|
clear()
public DataProfileAction.Export.Builder clear()| Returns | |
|---|---|
| Type | Description |
DataProfileAction.Export.Builder |
|
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_discoveryand table will be nameddiscovery_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.
- See Sample queries for your BigQuery table.
- 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.
- The best practice is to use the same table for an entire organization so that you can take advantage of the provided Looker reports. 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 | |
|---|---|
| Type | Description |
DataProfileAction.Export.Builder |
|
clearSampleFindingsTable()
public DataProfileAction.Export.Builder clearSampleFindingsTable()Store sample data profile findings 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 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 | |
|---|---|
| Type | Description |
DataProfileAction.Export.Builder |
|
getDefaultInstanceForType()
public DataProfileAction.Export getDefaultInstanceForType()| Returns | |
|---|---|
| Type | Description |
DataProfileAction.Export |
|
getDescriptorForType()
public Descriptors.Descriptor getDescriptorForType()| Returns | |
|---|---|
| Type | Description |
Descriptor |
|
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_discoveryand table will be nameddiscovery_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.
- See Sample queries for your BigQuery table.
- 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.
- The best practice is to use the same table for an entire organization so that you can take advantage of the provided Looker reports. 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 | |
|---|---|
| Type | Description |
BigQueryTable |
The profileTable. |
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_discoveryand table will be nameddiscovery_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.
- See Sample queries for your BigQuery table.
- 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.
- The best practice is to use the same table for an entire organization so that you can take advantage of the provided Looker reports. 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 | |
|---|---|
| Type | Description |
BigQueryTable.Builder |
|
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_discoveryand table will be nameddiscovery_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.
- See Sample queries for your BigQuery table.
- 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.
- The best practice is to use the same table for an entire organization so that you can take advantage of the provided Looker reports. 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 | |
|---|---|
| Type | Description |
BigQueryTableOrBuilder |
|
getSampleFindingsTable()
public BigQueryTable getSampleFindingsTable()Store sample data profile findings 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 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 | |
|---|---|
| Type | Description |
BigQueryTable |
The sampleFindingsTable. |
getSampleFindingsTableBuilder()
public BigQueryTable.Builder getSampleFindingsTableBuilder()Store sample data profile findings 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 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 | |
|---|---|
| Type | Description |
BigQueryTable.Builder |
|
getSampleFindingsTableOrBuilder()
public BigQueryTableOrBuilder getSampleFindingsTableOrBuilder()Store sample data profile findings 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 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 | |
|---|---|
| Type | Description |
BigQueryTableOrBuilder |
|
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_discoveryand table will be nameddiscovery_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.
- See Sample queries for your BigQuery table.
- 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.
- The best practice is to use the same table for an entire organization so that you can take advantage of the provided Looker reports. 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 | |
|---|---|
| Type | Description |
boolean |
Whether the profileTable field is set. |
hasSampleFindingsTable()
public boolean hasSampleFindingsTable()Store sample data profile findings 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 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 | |
|---|---|
| Type | Description |
boolean |
Whether the sampleFindingsTable field is set. |
internalGetFieldAccessorTable()
protected GeneratedMessage.FieldAccessorTable internalGetFieldAccessorTable()| Returns | |
|---|---|
| Type | Description |
FieldAccessorTable |
|
isInitialized()
public final boolean isInitialized()| Returns | |
|---|---|
| Type | Description |
boolean |
|
mergeFrom(DataProfileAction.Export other)
public DataProfileAction.Export.Builder mergeFrom(DataProfileAction.Export other)| Parameter | |
|---|---|
| Name | Description |
other |
DataProfileAction.Export |
| Returns | |
|---|---|
| Type | Description |
DataProfileAction.Export.Builder |
|
mergeFrom(CodedInputStream input, ExtensionRegistryLite extensionRegistry)
public DataProfileAction.Export.Builder mergeFrom(CodedInputStream input, ExtensionRegistryLite extensionRegistry)| Parameters | |
|---|---|
| Name | Description |
input |
CodedInputStream |
extensionRegistry |
ExtensionRegistryLite |
| Returns | |
|---|---|
| Type | Description |
DataProfileAction.Export.Builder |
|
| Exceptions | |
|---|---|
| Type | Description |
IOException |
|
mergeFrom(Message other)
public DataProfileAction.Export.Builder mergeFrom(Message other)| Parameter | |
|---|---|
| Name | Description |
other |
Message |
| Returns | |
|---|---|
| Type | Description |
DataProfileAction.Export.Builder |
|
mergeProfileTable(BigQueryTable value)
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_discoveryand table will be nameddiscovery_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.
- See Sample queries for your BigQuery table.
- 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.
- The best practice is to use the same table for an entire organization so that you can take advantage of the provided Looker reports. 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;
| Parameter | |
|---|---|
| Name | Description |
value |
BigQueryTable |
| Returns | |
|---|---|
| Type | Description |
DataProfileAction.Export.Builder |
|
mergeSampleFindingsTable(BigQueryTable value)
public DataProfileAction.Export.Builder mergeSampleFindingsTable(BigQueryTable value)Store sample data profile findings 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 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;
| Parameter | |
|---|---|
| Name | Description |
value |
BigQueryTable |
| Returns | |
|---|---|
| Type | Description |
DataProfileAction.Export.Builder |
|
setProfileTable(BigQueryTable value)
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_discoveryand table will be nameddiscovery_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.
- See Sample queries for your BigQuery table.
- 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.
- The best practice is to use the same table for an entire organization so that you can take advantage of the provided Looker reports. 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;
| Parameter | |
|---|---|
| Name | Description |
value |
BigQueryTable |
| Returns | |
|---|---|
| Type | Description |
DataProfileAction.Export.Builder |
|
setProfileTable(BigQueryTable.Builder builderForValue)
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_discoveryand table will be nameddiscovery_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.
- See Sample queries for your BigQuery table.
- 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.
- The best practice is to use the same table for an entire organization so that you can take advantage of the provided Looker reports. 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;
| Parameter | |
|---|---|
| Name | Description |
builderForValue |
BigQueryTable.Builder |
| Returns | |
|---|---|
| Type | Description |
DataProfileAction.Export.Builder |
|
setSampleFindingsTable(BigQueryTable value)
public DataProfileAction.Export.Builder setSampleFindingsTable(BigQueryTable value)Store sample data profile findings 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 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;
| Parameter | |
|---|---|
| Name | Description |
value |
BigQueryTable |
| Returns | |
|---|---|
| Type | Description |
DataProfileAction.Export.Builder |
|
setSampleFindingsTable(BigQueryTable.Builder builderForValue)
public DataProfileAction.Export.Builder setSampleFindingsTable(BigQueryTable.Builder builderForValue)Store sample data profile findings 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 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;
| Parameter | |
|---|---|
| Name | Description |
builderForValue |
BigQueryTable.Builder |
| Returns | |
|---|---|
| Type | Description |
DataProfileAction.Export.Builder |
|