Package com.pulumi.aws.timestreamquery.inputs

Class ScheduledQueryLastRunSummaryQueryInsightsResponseArgs

  • public final class ScheduledQueryLastRunSummaryQueryInsightsResponseArgs
extends com.pulumi.resources.ResourceArgs

    • Method Detail

      • outputBytes

        public java.util.Optional<com.pulumi.core.Output<java.lang.Integer>> outputBytes()
        Returns:
        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.

      • outputRows

        public java.util.Optional<com.pulumi.core.Output<java.lang.Integer>> outputRows()
        Returns:
        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.

      • querySpatialCoverages

        public java.util.Optional<com.pulumi.core.Output<java.util.List<ScheduledQueryLastRunSummaryQueryInsightsResponseQuerySpatialCoverageArgs>>> querySpatialCoverages()
        Returns:
        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. See `recently_failed_runs.query_insights_response.query_spatial_coverage` Block for details.

      • queryTableCount

        public java.util.Optional<com.pulumi.core.Output<java.lang.Integer>> queryTableCount()
        Returns:
        Number of tables in the query.

      • queryTemporalRanges

        public java.util.Optional<com.pulumi.core.Output<java.util.List<ScheduledQueryLastRunSummaryQueryInsightsResponseQueryTemporalRangeArgs>>> queryTemporalRanges()
        Returns:
        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. See `recently_failed_runs.query_insights_response.query_temporal_range` Block for details.