Interface StorageConfig.TimespanConfigOrBuilder (3.18.0)

When the job is started by a JobTrigger we will automatically figure out a valid start_time to avoid scanning files that have not been modified since the last time the JobTrigger executed. This will be based on the time of the execution of the last run of the JobTrigger or the timespan end_time used in the last run of the JobTrigger.

bool enable_auto_population_of_timespan_config = 4;

Exclude files, tables, or rows newer than this value. If not set, no upper time limit is applied.

.google.protobuf.Timestamp end_time = 2;

Exclude files, tables, or rows newer than this value. If not set, no upper time limit is applied.

.google.protobuf.Timestamp end_time = 2;

Exclude files, tables, or rows older than this value. If not set, no lower time limit is applied.

.google.protobuf.Timestamp start_time = 1;

Exclude files, tables, or rows older than this value. If not set, no lower time limit is applied.

.google.protobuf.Timestamp start_time = 1;

Specification of the field containing the timestamp of scanned items. Used for data sources like Datastore and BigQuery. <b>For BigQuery</b> If this value is not specified and the table was modified between the given start and end times, the entire table will be scanned. If this value is specified, then rows are filtered based on the given start and end times. Rows with a NULL value in the provided BigQuery column are skipped. Valid data types of the provided BigQuery column are: INTEGER, DATE, TIMESTAMP, and DATETIME. If your BigQuery table is partitioned at ingestion time, you can use any of the following pseudo-columns as your timestamp field. When used with Cloud DLP, these pseudo-column names are case sensitive. <ul> <li><code>_PARTITIONTIME</code></li> <li><code>_PARTITIONDATE</code></li> <li><code>_PARTITION_LOAD_TIME</code></li> </ul> <b>For Datastore</b> If this value is specified, then entities are filtered based on the given start and end times. If an entity does not contain the provided timestamp property or contains empty or invalid values, then it is included. Valid data types of the provided timestamp property are: TIMESTAMP. See the known issue related to this operation.

.google.privacy.dlp.v2.FieldId timestamp_field = 3;

Specification of the field containing the timestamp of scanned items. Used for data sources like Datastore and BigQuery. <b>For BigQuery</b> If this value is not specified and the table was modified between the given start and end times, the entire table will be scanned. If this value is specified, then rows are filtered based on the given start and end times. Rows with a NULL value in the provided BigQuery column are skipped. Valid data types of the provided BigQuery column are: INTEGER, DATE, TIMESTAMP, and DATETIME. If your BigQuery table is partitioned at ingestion time, you can use any of the following pseudo-columns as your timestamp field. When used with Cloud DLP, these pseudo-column names are case sensitive. <ul> <li><code>_PARTITIONTIME</code></li> <li><code>_PARTITIONDATE</code></li> <li><code>_PARTITION_LOAD_TIME</code></li> </ul> <b>For Datastore</b> If this value is specified, then entities are filtered based on the given start and end times. If an entity does not contain the provided timestamp property or contains empty or invalid values, then it is included. Valid data types of the provided timestamp property are: TIMESTAMP. See the known issue related to this operation.

.google.privacy.dlp.v2.FieldId timestamp_field = 3;

Exclude files, tables, or rows newer than this value. If not set, no upper time limit is applied.

.google.protobuf.Timestamp end_time = 2;

Exclude files, tables, or rows older than this value. If not set, no lower time limit is applied.

.google.protobuf.Timestamp start_time = 1;

Specification of the field containing the timestamp of scanned items. Used for data sources like Datastore and BigQuery. <b>For BigQuery</b> If this value is not specified and the table was modified between the given start and end times, the entire table will be scanned. If this value is specified, then rows are filtered based on the given start and end times. Rows with a NULL value in the provided BigQuery column are skipped. Valid data types of the provided BigQuery column are: INTEGER, DATE, TIMESTAMP, and DATETIME. If your BigQuery table is partitioned at ingestion time, you can use any of the following pseudo-columns as your timestamp field. When used with Cloud DLP, these pseudo-column names are case sensitive. <ul> <li><code>_PARTITIONTIME</code></li> <li><code>_PARTITIONDATE</code></li> <li><code>_PARTITION_LOAD_TIME</code></li> </ul> <b>For Datastore</b> If this value is specified, then entities are filtered based on the given start and end times. If an entity does not contain the provided timestamp property or contains empty or invalid values, then it is included. Valid data types of the provided timestamp property are: TIMESTAMP. See the known issue related to this operation.

.google.privacy.dlp.v2.FieldId timestamp_field = 3;