pulumi-aws-kotlin/com.pulumi.aws.timestreamquery.kotlin.outputs/ScheduledQueryLastRunSummaryQueryInsightsResponse

ScheduledQueryLastRunSummaryQueryInsightsResponse

data class ScheduledQueryLastRunSummaryQueryInsightsResponse(val outputBytes: Int? = null, val outputRows: Int? = null, val querySpatialCoverages: List<ScheduledQueryLastRunSummaryQueryInsightsResponseQuerySpatialCoverage>? = null, val queryTableCount: Int? = null, val queryTemporalRanges: List<ScheduledQueryLastRunSummaryQueryInsightsResponseQueryTemporalRange>? = null)

Constructors

constructor(outputBytes: Int? = null, outputRows: Int? = null, querySpatialCoverages: List<ScheduledQueryLastRunSummaryQueryInsightsResponseQuerySpatialCoverage>? = null, queryTableCount: Int? = null, queryTemporalRanges: List<ScheduledQueryLastRunSummaryQueryInsightsResponseQueryTemporalRange>? = null)

Types

Link copied to clipboard
object Companion

Properties

Link copied to clipboard
val outputBytes: Int? = null

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.

Link copied to clipboard
val outputRows: Int? = null

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.

Link copied to clipboard
val querySpatialCoverages: List<ScheduledQueryLastRunSummaryQueryInsightsResponseQuerySpatialCoverage>? = null

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.

Link copied to clipboard
val queryTableCount: Int? = null

Number of tables in the query.

Link copied to clipboard
val queryTemporalRanges: List<ScheduledQueryLastRunSummaryQueryInsightsResponseQueryTemporalRange>? = null

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.