ScheduledQueryInsightsResponse
¶
Source code in docs_src/capo_timestream_query/types/scheduled_query_insights_response.py
output_bytes
instance-attribute
¶
output_bytes: NotRequired[Long]
Indicates the size of query result set in bytes. You can use this data to validate if the result set has changed as part of the query tuning exercise.
output_rows
instance-attribute
¶
output_rows: NotRequired[Long]
Indicates the total number of rows returned as part of the query result set. You can use this data to validate if the number of rows in the result set have changed as part of the query tuning exercise.
query_spatial_coverage
instance-attribute
¶
query_spatial_coverage: NotRequired[QuerySpatialCoverage]
Provides insights into the spatial coverage of the query, including the table with sub-optimal (max) spatial pruning. This information can help you identify areas for improvement in your partitioning strategy to enhance spatial pruning.
query_table_count
instance-attribute
¶
query_table_count: NotRequired[Long]
Indicates the number of tables in the query.
query_temporal_range
instance-attribute
¶
query_temporal_range: NotRequired[QueryTemporalRange]
Provides insights into the temporal range of the query, including the table with the largest (max) time range. Following are some of the potential options for optimizing time-based pruning:
-
Add missing time-predicates.
-
Remove functions around the time predicates.
-
Add time predicates to all the sub-queries.