Class TimespanConfig (2.0.2)

Version 2.0.2

• 3.25.1 (latest)
• 3.25.0
• 3.24.0
• 3.23.0
• 3.22.0
• 3.20.0
• 3.19.0
• 3.18.1
• 3.17.0
• 3.16.0
• 3.15.3
• 3.14.0
• 3.13.0
• 3.12.3
• 3.11.1
• 3.10.1
• 3.9.2
• 3.8.1
• 3.7.1
• 3.6.2
• 3.5.0
• 3.4.0
• 3.3.1
• 3.2.4
• 3.1.1
• 3.0.1
• 2.0.2
• 1.0.2
• 0.15.2
• 0.14.0
• 0.13.0
• 0.12.1

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
Name	Description
start_time	.timestamp.Timestamp Exclude files or rows older than this value.
end_time	.timestamp.Timestamp Exclude files or rows newer than this value. If set to zero, no upper time limit is applied.
timestamp_field	.storage.FieldId Specification of the field containing the timestamp of scanned items. Used for data sources like Datastore and BigQuery. For BigQuery: Required to filter out rows based on the given start and end times. If not specified and the table was modified between the given start and end times, the entire table will be scanned. The valid data types of the timestamp field are: INTEGER, DATE, TIMESTAMP, or DATETIME BigQuery column. For Datastore. Valid data types of the timestamp field are: TIMESTAMP. Datastore entity will be scanned if the timestamp property does not exist or its value is empty or invalid.
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.