Struct QueryFluentBuilder

pub struct QueryFluentBuilder { /* private fields */ }

Fluent builder constructing a request to Query.

Query is a synchronous operation that enables you to run a query against your Amazon Timestream data.

If you enabled QueryInsights, this API also returns insights and metrics related to the query that you executed. QueryInsights helps with performance tuning of your query. For more information about QueryInsights, see Using query insights to optimize queries in Amazon Timestream.

The maximum number of Query API requests you're allowed to make with QueryInsights enabled is 1 query per second (QPS). If you exceed this query rate, it might result in throttling.

Query will time out after 60 seconds. You must update the default timeout in the SDK to support a timeout of 60 seconds. See the code sample for details.

Your query request will fail in the following cases:

• If you submit a Query request with the same client token outside of the 5-minute idempotency window.

• If you submit a Query request with the same client token, but change other parameters, within the 5-minute idempotency window.

• If the size of the row (including the query metadata) exceeds 1 MB, then the query will fail with the following error message:

  Query aborted as max page response size has been exceeded by the output result row

• If the IAM principal of the query initiator and the result reader are not the same and/or the query initiator and the result reader do not have the same query string in the query requests, the query will fail with an Invalid pagination token error.

Implementations

impl QueryFluentBuilder

pub fn as_input(&self) -> &QueryInputBuilder

Access the Query as a reference.

pub async fn send( self, ) -> Result<QueryOutput, SdkError<QueryError, HttpResponse>>

Sends the request and returns the response.

If an error occurs, an SdkError will be returned with additional details that can be matched against.

By default, any retryable failures will be retried twice. Retry behavior is configurable with the RetryConfig, which can be set when configuring the client.

pub fn customize(self) -> CustomizableOperation<QueryOutput, QueryError, Self>

Consumes this builder, creating a customizable operation that can be modified before being sent.

pub fn query_string(self, input: impl Into<String>) -> Self

The query to be run by Timestream.

pub fn set_query_string(self, input: Option<String>) -> Self

The query to be run by Timestream.

pub fn get_query_string(&self) -> &Option<String>

The query to be run by Timestream.

pub fn client_token(self, input: impl Into<String>) -> Self

Unique, case-sensitive string of up to 64 ASCII characters specified when a Query request is made. Providing a ClientToken makes the call to Query idempotent. This means that running the same query repeatedly will produce the same result. In other words, making multiple identical Query requests has the same effect as making a single request. When using ClientToken in a query, note the following:

• If the Query API is instantiated without a ClientToken, the Query SDK generates a ClientToken on your behalf.

• If the Query invocation only contains the ClientToken but does not include a NextToken, that invocation of Query is assumed to be a new query run.

• If the invocation contains NextToken, that particular invocation is assumed to be a subsequent invocation of a prior call to the Query API, and a result set is returned.

• After 4 hours, any request with the same ClientToken is treated as a new request.

pub fn set_client_token(self, input: Option<String>) -> Self

Unique, case-sensitive string of up to 64 ASCII characters specified when a Query request is made. Providing a ClientToken makes the call to Query idempotent. This means that running the same query repeatedly will produce the same result. In other words, making multiple identical Query requests has the same effect as making a single request. When using ClientToken in a query, note the following:

• If the Query API is instantiated without a ClientToken, the Query SDK generates a ClientToken on your behalf.

• If the Query invocation only contains the ClientToken but does not include a NextToken, that invocation of Query is assumed to be a new query run.

• If the invocation contains NextToken, that particular invocation is assumed to be a subsequent invocation of a prior call to the Query API, and a result set is returned.

• After 4 hours, any request with the same ClientToken is treated as a new request.

pub fn get_client_token(&self) -> &Option<String>

Unique, case-sensitive string of up to 64 ASCII characters specified when a Query request is made. Providing a ClientToken makes the call to Query idempotent. This means that running the same query repeatedly will produce the same result. In other words, making multiple identical Query requests has the same effect as making a single request. When using ClientToken in a query, note the following:

• If the Query API is instantiated without a ClientToken, the Query SDK generates a ClientToken on your behalf.

• If the Query invocation only contains the ClientToken but does not include a NextToken, that invocation of Query is assumed to be a new query run.

• If the invocation contains NextToken, that particular invocation is assumed to be a subsequent invocation of a prior call to the Query API, and a result set is returned.

• After 4 hours, any request with the same ClientToken is treated as a new request.

pub fn next_token(self, input: impl Into<String>) -> Self

A pagination token used to return a set of results. When the Query API is invoked using NextToken, that particular invocation is assumed to be a subsequent invocation of a prior call to Query, and a result set is returned. However, if the Query invocation only contains the ClientToken, that invocation of Query is assumed to be a new query run.

Note the following when using NextToken in a query:

• A pagination token can be used for up to five Query invocations, OR for a duration of up to 1 hour – whichever comes first.

• Using the same NextToken will return the same set of records. To keep paginating through the result set, you must to use the most recent nextToken.

• Suppose a Query invocation returns two NextToken values, TokenA and TokenB. If TokenB is used in a subsequent Query invocation, then TokenA is invalidated and cannot be reused.

• To request a previous result set from a query after pagination has begun, you must re-invoke the Query API.

• The latest NextToken should be used to paginate until null is returned, at which point a new NextToken should be used.

• If the IAM principal of the query initiator and the result reader are not the same and/or the query initiator and the result reader do not have the same query string in the query requests, the query will fail with an Invalid pagination token error.

pub fn set_next_token(self, input: Option<String>) -> Self

A pagination token used to return a set of results. When the Query API is invoked using NextToken, that particular invocation is assumed to be a subsequent invocation of a prior call to Query, and a result set is returned. However, if the Query invocation only contains the ClientToken, that invocation of Query is assumed to be a new query run.

Note the following when using NextToken in a query:

• A pagination token can be used for up to five Query invocations, OR for a duration of up to 1 hour – whichever comes first.

• Using the same NextToken will return the same set of records. To keep paginating through the result set, you must to use the most recent nextToken.

• Suppose a Query invocation returns two NextToken values, TokenA and TokenB. If TokenB is used in a subsequent Query invocation, then TokenA is invalidated and cannot be reused.

• To request a previous result set from a query after pagination has begun, you must re-invoke the Query API.

• The latest NextToken should be used to paginate until null is returned, at which point a new NextToken should be used.

• If the IAM principal of the query initiator and the result reader are not the same and/or the query initiator and the result reader do not have the same query string in the query requests, the query will fail with an Invalid pagination token error.

pub fn get_next_token(&self) -> &Option<String>

A pagination token used to return a set of results. When the Query API is invoked using NextToken, that particular invocation is assumed to be a subsequent invocation of a prior call to Query, and a result set is returned. However, if the Query invocation only contains the ClientToken, that invocation of Query is assumed to be a new query run.

Note the following when using NextToken in a query:

• A pagination token can be used for up to five Query invocations, OR for a duration of up to 1 hour – whichever comes first.

• Using the same NextToken will return the same set of records. To keep paginating through the result set, you must to use the most recent nextToken.

• Suppose a Query invocation returns two NextToken values, TokenA and TokenB. If TokenB is used in a subsequent Query invocation, then TokenA is invalidated and cannot be reused.

• To request a previous result set from a query after pagination has begun, you must re-invoke the Query API.

• The latest NextToken should be used to paginate until null is returned, at which point a new NextToken should be used.

• If the IAM principal of the query initiator and the result reader are not the same and/or the query initiator and the result reader do not have the same query string in the query requests, the query will fail with an Invalid pagination token error.

pub fn max_rows(self, input: i32) -> Self

The total number of rows to be returned in the Query output. The initial run of Query with a MaxRows value specified will return the result set of the query in two cases:

• The size of the result is less than 1MB.

• The number of rows in the result set is less than the value of maxRows.

Otherwise, the initial invocation of Query only returns a NextToken, which can then be used in subsequent calls to fetch the result set. To resume pagination, provide the NextToken value in the subsequent command.

If the row size is large (e.g. a row has many columns), Timestream may return fewer rows to keep the response size from exceeding the 1 MB limit. If MaxRows is not provided, Timestream will send the necessary number of rows to meet the 1 MB limit.

pub fn set_max_rows(self, input: Option<i32>) -> Self

The total number of rows to be returned in the Query output. The initial run of Query with a MaxRows value specified will return the result set of the query in two cases:

• The size of the result is less than 1MB.

• The number of rows in the result set is less than the value of maxRows.

Otherwise, the initial invocation of Query only returns a NextToken, which can then be used in subsequent calls to fetch the result set. To resume pagination, provide the NextToken value in the subsequent command.

If the row size is large (e.g. a row has many columns), Timestream may return fewer rows to keep the response size from exceeding the 1 MB limit. If MaxRows is not provided, Timestream will send the necessary number of rows to meet the 1 MB limit.

pub fn get_max_rows(&self) -> &Option<i32>

The total number of rows to be returned in the Query output. The initial run of Query with a MaxRows value specified will return the result set of the query in two cases:

• The size of the result is less than 1MB.

• The number of rows in the result set is less than the value of maxRows.

Otherwise, the initial invocation of Query only returns a NextToken, which can then be used in subsequent calls to fetch the result set. To resume pagination, provide the NextToken value in the subsequent command.

If the row size is large (e.g. a row has many columns), Timestream may return fewer rows to keep the response size from exceeding the 1 MB limit. If MaxRows is not provided, Timestream will send the necessary number of rows to meet the 1 MB limit.

pub fn query_insights(self, input: QueryInsights) -> Self

Encapsulates settings for enabling QueryInsights.

Enabling QueryInsights returns insights and metrics in addition to query results for the query that you executed. You can use QueryInsights to tune your query performance.

pub fn set_query_insights(self, input: Option<QueryInsights>) -> Self

Encapsulates settings for enabling QueryInsights.

Enabling QueryInsights returns insights and metrics in addition to query results for the query that you executed. You can use QueryInsights to tune your query performance.

pub fn get_query_insights(&self) -> &Option<QueryInsights>

Encapsulates settings for enabling QueryInsights.

Enabling QueryInsights returns insights and metrics in addition to query results for the query that you executed. You can use QueryInsights to tune your query performance.

Trait Implementations

impl Clone for QueryFluentBuilder

fn clone(&self) -> QueryFluentBuilder

Returns a duplicate of the value.

const fn clone_from(&mut self, source: &Self)

Performs copy-assignment from source.

impl Debug for QueryFluentBuilder

fn fmt(&self, f: &mut Formatter<'_>) -> Result

Formats the value using the given formatter.