Reference documentation and code samples for the Data Loss Prevention V2 Client class OutputStorageConfig.
Cloud repository for storing output.
Generated from protobuf message google.privacy.dlp.v2.OutputStorageConfig
Methods
__construct
Constructor.
Parameters | |
---|---|
Name | Description |
data |
array
Optional. Data for populating the Message object. |
↳ table |
Google\Cloud\Dlp\V2\BigQueryTable
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 |
↳ output_schema |
int
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 |
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.
Returns | |
---|---|
Type | Description |
Google\Cloud\Dlp\V2\BigQueryTable|null |
hasTable
setTable
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.
Parameter | |
---|---|
Name | Description |
var |
Google\Cloud\Dlp\V2\BigQueryTable
|
Returns | |
---|---|
Type | Description |
$this |
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.
Returns | |
---|---|
Type | Description |
int |
setOutputSchema
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.
Parameter | |
---|---|
Name | Description |
var |
int
|
Returns | |
---|---|
Type | Description |
$this |
getType
Returns | |
---|---|
Type | Description |
string |