Struct aws_sdk_iotsitewise::types::builders::TumblingWindowBuilder

#[non_exhaustive]
pub struct TumblingWindowBuilder { /* private fields */ }

A builder for TumblingWindow.

Implementations

impl TumblingWindowBuilder

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

The time interval for the tumbling window. The interval time must be between 1 minute and 1 week.

IoT SiteWise computes the 1w interval the end of Sunday at midnight each week (UTC), the 1d interval at the end of each day at midnight (UTC), the 1h interval at the end of each hour, and so on.

When IoT SiteWise aggregates data points for metric computations, the start of each interval is exclusive and the end of each interval is inclusive. IoT SiteWise places the computed data point at the end of the interval.

This field is required.

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

The time interval for the tumbling window. The interval time must be between 1 minute and 1 week.

IoT SiteWise computes the 1w interval the end of Sunday at midnight each week (UTC), the 1d interval at the end of each day at midnight (UTC), the 1h interval at the end of each hour, and so on.

When IoT SiteWise aggregates data points for metric computations, the start of each interval is exclusive and the end of each interval is inclusive. IoT SiteWise places the computed data point at the end of the interval.

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

The time interval for the tumbling window. The interval time must be between 1 minute and 1 week.

IoT SiteWise computes the 1w interval the end of Sunday at midnight each week (UTC), the 1d interval at the end of each day at midnight (UTC), the 1h interval at the end of each hour, and so on.

When IoT SiteWise aggregates data points for metric computations, the start of each interval is exclusive and the end of each interval is inclusive. IoT SiteWise places the computed data point at the end of the interval.

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

The offset for the tumbling window. The offset parameter accepts the following:

• The offset time.

  For example, if you specify 18h for offset and 1d for interval, IoT SiteWise aggregates data in one of the following ways:

  • If you create the metric before or at 6 PM (UTC), you get the first aggregation result at 6 PM (UTC) on the day when you create the metric.

  • If you create the metric after 6 PM (UTC), you get the first aggregation result at 6 PM (UTC) the next day.

• The ISO 8601 format.

  For example, if you specify PT18H for offset and 1d for interval, IoT SiteWise aggregates data in one of the following ways:

  • If you create the metric before or at 6 PM (UTC), you get the first aggregation result at 6 PM (UTC) on the day when you create the metric.

  • If you create the metric after 6 PM (UTC), you get the first aggregation result at 6 PM (UTC) the next day.

• The 24-hour clock.

  For example, if you specify 00:03:00 for offset, 5m for interval, and you create the metric at 2 PM (UTC), you get the first aggregation result at 2:03 PM (UTC). You get the second aggregation result at 2:08 PM (UTC).

• The offset time zone.

  For example, if you specify 2021-07-23T18:00-08 for offset and 1d for interval, IoT SiteWise aggregates data in one of the following ways:

  • If you create the metric before or at 6 PM (PST), you get the first aggregation result at 6 PM (PST) on the day when you create the metric.

  • If you create the metric after 6 PM (PST), you get the first aggregation result at 6 PM (PST) the next day.

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

The offset for the tumbling window. The offset parameter accepts the following:

• The offset time.

  For example, if you specify 18h for offset and 1d for interval, IoT SiteWise aggregates data in one of the following ways:

  • If you create the metric before or at 6 PM (UTC), you get the first aggregation result at 6 PM (UTC) on the day when you create the metric.

  • If you create the metric after 6 PM (UTC), you get the first aggregation result at 6 PM (UTC) the next day.

• The ISO 8601 format.

  For example, if you specify PT18H for offset and 1d for interval, IoT SiteWise aggregates data in one of the following ways:

  • If you create the metric before or at 6 PM (UTC), you get the first aggregation result at 6 PM (UTC) on the day when you create the metric.

  • If you create the metric after 6 PM (UTC), you get the first aggregation result at 6 PM (UTC) the next day.

• The 24-hour clock.

  For example, if you specify 00:03:00 for offset, 5m for interval, and you create the metric at 2 PM (UTC), you get the first aggregation result at 2:03 PM (UTC). You get the second aggregation result at 2:08 PM (UTC).

• The offset time zone.

  For example, if you specify 2021-07-23T18:00-08 for offset and 1d for interval, IoT SiteWise aggregates data in one of the following ways:

  • If you create the metric before or at 6 PM (PST), you get the first aggregation result at 6 PM (PST) on the day when you create the metric.

  • If you create the metric after 6 PM (PST), you get the first aggregation result at 6 PM (PST) the next day.

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

The offset for the tumbling window. The offset parameter accepts the following:

• The offset time.

  For example, if you specify 18h for offset and 1d for interval, IoT SiteWise aggregates data in one of the following ways:

  • If you create the metric before or at 6 PM (UTC), you get the first aggregation result at 6 PM (UTC) on the day when you create the metric.

  • If you create the metric after 6 PM (UTC), you get the first aggregation result at 6 PM (UTC) the next day.

• The ISO 8601 format.

  For example, if you specify PT18H for offset and 1d for interval, IoT SiteWise aggregates data in one of the following ways:

  • If you create the metric before or at 6 PM (UTC), you get the first aggregation result at 6 PM (UTC) on the day when you create the metric.

  • If you create the metric after 6 PM (UTC), you get the first aggregation result at 6 PM (UTC) the next day.

• The 24-hour clock.

  For example, if you specify 00:03:00 for offset, 5m for interval, and you create the metric at 2 PM (UTC), you get the first aggregation result at 2:03 PM (UTC). You get the second aggregation result at 2:08 PM (UTC).

• The offset time zone.

  For example, if you specify 2021-07-23T18:00-08 for offset and 1d for interval, IoT SiteWise aggregates data in one of the following ways:

  • If you create the metric before or at 6 PM (PST), you get the first aggregation result at 6 PM (PST) on the day when you create the metric.

  • If you create the metric after 6 PM (PST), you get the first aggregation result at 6 PM (PST) the next day.

pub fn build(self) -> Result<TumblingWindow, BuildError>

Consumes the builder and constructs a TumblingWindow. This method will fail if any of the following fields are not set:

• interval

Trait Implementations

impl Clone for TumblingWindowBuilder

fn clone(&self) -> TumblingWindowBuilder

Returns a copy of the value.

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

Performs copy-assignment from source.

impl Debug for TumblingWindowBuilder

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

Formats the value using the given formatter.

impl Default for TumblingWindowBuilder

fn default() -> TumblingWindowBuilder

Returns the “default value” for a type.

impl PartialEq for TumblingWindowBuilder

fn eq(&self, other: &TumblingWindowBuilder) -> bool

This method tests for self and other values to be equal, and is used by ==.

fn ne(&self, other: &Rhs) -> bool

This method tests for !=. The default implementation is almost always sufficient, and should not be overridden without very good reason.

impl StructuralPartialEq for TumblingWindowBuilder