Class ScheduledQueryLastRunSummaryQueryInsightsResponseArgs.Builder
- java.lang.Object
-
- com.pulumi.aws.timestreamquery.inputs.ScheduledQueryLastRunSummaryQueryInsightsResponseArgs.Builder
-
- Enclosing class:
- ScheduledQueryLastRunSummaryQueryInsightsResponseArgs
public static final class ScheduledQueryLastRunSummaryQueryInsightsResponseArgs.Builder extends java.lang.Object
-
-
Constructor Summary
Constructors Constructor Description Builder()Builder(ScheduledQueryLastRunSummaryQueryInsightsResponseArgs defaults)
-
Method Summary
-
-
-
Constructor Detail
-
Builder
public Builder()
-
Builder
public Builder(ScheduledQueryLastRunSummaryQueryInsightsResponseArgs defaults)
-
-
Method Detail
-
outputBytes
public ScheduledQueryLastRunSummaryQueryInsightsResponseArgs.Builder outputBytes(@Nullable com.pulumi.core.Output<java.lang.Integer> outputBytes)
- Parameters:
outputBytes- 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.- Returns:
- builder
-
outputBytes
public ScheduledQueryLastRunSummaryQueryInsightsResponseArgs.Builder outputBytes(java.lang.Integer outputBytes)
- Parameters:
outputBytes- 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.- Returns:
- builder
-
outputRows
public ScheduledQueryLastRunSummaryQueryInsightsResponseArgs.Builder outputRows(@Nullable com.pulumi.core.Output<java.lang.Integer> outputRows)
- Parameters:
outputRows- 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.- Returns:
- builder
-
outputRows
public ScheduledQueryLastRunSummaryQueryInsightsResponseArgs.Builder outputRows(java.lang.Integer outputRows)
- Parameters:
outputRows- 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.- Returns:
- builder
-
querySpatialCoverages
public ScheduledQueryLastRunSummaryQueryInsightsResponseArgs.Builder querySpatialCoverages(@Nullable com.pulumi.core.Output<java.util.List<ScheduledQueryLastRunSummaryQueryInsightsResponseQuerySpatialCoverageArgs>> querySpatialCoverages)
- Parameters:
querySpatialCoverages- 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.- Returns:
- builder
-
querySpatialCoverages
public ScheduledQueryLastRunSummaryQueryInsightsResponseArgs.Builder querySpatialCoverages(java.util.List<ScheduledQueryLastRunSummaryQueryInsightsResponseQuerySpatialCoverageArgs> querySpatialCoverages)
- Parameters:
querySpatialCoverages- 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.- Returns:
- builder
-
querySpatialCoverages
public ScheduledQueryLastRunSummaryQueryInsightsResponseArgs.Builder querySpatialCoverages(ScheduledQueryLastRunSummaryQueryInsightsResponseQuerySpatialCoverageArgs... querySpatialCoverages)
- Parameters:
querySpatialCoverages- 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.- Returns:
- builder
-
queryTableCount
public ScheduledQueryLastRunSummaryQueryInsightsResponseArgs.Builder queryTableCount(@Nullable com.pulumi.core.Output<java.lang.Integer> queryTableCount)
- Parameters:
queryTableCount- Number of tables in the query.- Returns:
- builder
-
queryTableCount
public ScheduledQueryLastRunSummaryQueryInsightsResponseArgs.Builder queryTableCount(java.lang.Integer queryTableCount)
- Parameters:
queryTableCount- Number of tables in the query.- Returns:
- builder
-
queryTemporalRanges
public ScheduledQueryLastRunSummaryQueryInsightsResponseArgs.Builder queryTemporalRanges(@Nullable com.pulumi.core.Output<java.util.List<ScheduledQueryLastRunSummaryQueryInsightsResponseQueryTemporalRangeArgs>> queryTemporalRanges)
- Parameters:
queryTemporalRanges- 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.- Returns:
- builder
-
queryTemporalRanges
public ScheduledQueryLastRunSummaryQueryInsightsResponseArgs.Builder queryTemporalRanges(java.util.List<ScheduledQueryLastRunSummaryQueryInsightsResponseQueryTemporalRangeArgs> queryTemporalRanges)
- Parameters:
queryTemporalRanges- 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.- Returns:
- builder
-
queryTemporalRanges
public ScheduledQueryLastRunSummaryQueryInsightsResponseArgs.Builder queryTemporalRanges(ScheduledQueryLastRunSummaryQueryInsightsResponseQueryTemporalRangeArgs... queryTemporalRanges)
- Parameters:
queryTemporalRanges- 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.- Returns:
- builder
-
build
public ScheduledQueryLastRunSummaryQueryInsightsResponseArgs build()
-
-