Reference documentation and code samples for the Data Loss Prevention V2 Client class DiscoveryCloudSqlGenerationCadence.
How often existing tables should have their profiles refreshed.
New tables are scanned as quickly as possible depending on system capacity.
Generated from protobuf message google.privacy.dlp.v2.DiscoveryCloudSqlGenerationCadence
Namespace
Google \ Cloud \ Dlp \ V2Methods
__construct
Constructor.
data
array
Optional. Data for populating the Message object.
↳ schema_modified_cadence
Google\Cloud\Dlp\V2\DiscoveryCloudSqlGenerationCadence\SchemaModifiedCadence
When to reprofile if the schema has changed.
↳ refresh_frequency
int
Data changes (non-schema changes) in Cloud SQL tables can't trigger reprofiling. If you set this field, profiles are refreshed at this frequency regardless of whether the underlying tables have changed. Defaults to never.
getSchemaModifiedCadence
When to reprofile if the schema has changed.
hasSchemaModifiedCadence
clearSchemaModifiedCadence
setSchemaModifiedCadence
When to reprofile if the schema has changed.
$this
getRefreshFrequency
Data changes (non-schema changes) in Cloud SQL tables can't trigger reprofiling. If you set this field, profiles are refreshed at this frequency regardless of whether the underlying tables have changed.
Defaults to never.
int
setRefreshFrequency
Data changes (non-schema changes) in Cloud SQL tables can't trigger reprofiling. If you set this field, profiles are refreshed at this frequency regardless of whether the underlying tables have changed.
Defaults to never.
var
int
$this
