Class TimespanConfig (3.8.1)

Stay organized with collections Save and categorize content based on your preferences.
TimespanConfig(mapping=None, *, ignore_unknown_fields=False, **kwargs)

Configuration of the timespan of the items to include in scanning. Currently only supported when inspecting Google Cloud Storage and BigQuery.

Attributes

NameDescription
start_time google.protobuf.timestamp_pb2.Timestamp
Exclude files, tables, or rows older than this value. If not set, no lower time limit is applied.
end_time google.protobuf.timestamp_pb2.Timestamp
Exclude files, tables, or rows newer than this value. If not set, no upper time limit is applied.
timestamp_field google.cloud.dlp_v2.types.FieldId
Specification of the field containing the timestamp of scanned items. Used for data sources like Datastore and BigQuery. For BigQuery: 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``. For Datastore: 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``.
enable_auto_population_of_timespan_config bool
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.

Inheritance

builtins.object > proto.message.Message > TimespanConfig