Struct CreateDatasetInput

#[non_exhaustive]
pub struct CreateDatasetInput {
    pub dataset_name: Option<String>,
    pub actions: Option<Vec<DatasetAction>>,
    pub triggers: Option<Vec<DatasetTrigger>>,
    pub content_delivery_rules: Option<Vec<DatasetContentDeliveryRule>>,
    pub retention_period: Option<RetentionPeriod>,
    pub versioning_configuration: Option<VersioningConfiguration>,
    pub tags: Option<Vec<Tag>>,
    pub late_data_rules: Option<Vec<LateDataRule>>,
}

Fields (Non-exhaustive)

Non-exhaustive structs could have additional fields added in future. Therefore, non-exhaustive structs cannot be constructed in external crates using the traditional Struct { .. } syntax; cannot be matched against without a wildcard ..; and struct update syntax will not work.

dataset_name: Option<String>

The name of the dataset.

actions: Option<Vec<DatasetAction>>

A list of actions that create the dataset contents.

triggers: Option<Vec<DatasetTrigger>>

A list of triggers. A trigger causes dataset contents to be populated at a specified time interval or when another dataset's contents are created. The list of triggers can be empty or contain up to five DataSetTrigger objects.

content_delivery_rules: Option<Vec<DatasetContentDeliveryRule>>

When dataset contents are created, they are delivered to destinations specified here.

retention_period: Option<RetentionPeriod>

Optional. How long, in days, versions of dataset contents are kept for the dataset. If not specified or set to null, versions of dataset contents are retained for at most 90 days. The number of versions of dataset contents retained is determined by the versioningConfiguration parameter. For more information, see Keeping Multiple Versions of IoT Analytics datasets in the IoT Analytics User Guide.

versioning_configuration: Option<VersioningConfiguration>

Optional. How many versions of dataset contents are kept. If not specified or set to null, only the latest version plus the latest succeeded version (if they are different) are kept for the time period specified by the retentionPeriod parameter. For more information, see Keeping Multiple Versions of IoT Analytics datasets in the IoT Analytics User Guide.

tags: Option<Vec<Tag>>

Metadata which can be used to manage the dataset.

late_data_rules: Option<Vec<LateDataRule>>

A list of data rules that send notifications to CloudWatch, when data arrives late. To specify lateDataRules, the dataset must use a DeltaTimer filter.

Implementations

impl CreateDatasetInput

pub fn dataset_name(&self) -> Option<&str>

The name of the dataset.

pub fn actions(&self) -> &[DatasetAction]

A list of actions that create the dataset contents.

If no value was sent for this field, a default will be set. If you want to determine if no value was sent, use .actions.is_none().

pub fn triggers(&self) -> &[DatasetTrigger]

A list of triggers. A trigger causes dataset contents to be populated at a specified time interval or when another dataset's contents are created. The list of triggers can be empty or contain up to five DataSetTrigger objects.

If no value was sent for this field, a default will be set. If you want to determine if no value was sent, use .triggers.is_none().

pub fn content_delivery_rules(&self) -> &[DatasetContentDeliveryRule]

When dataset contents are created, they are delivered to destinations specified here.

If no value was sent for this field, a default will be set. If you want to determine if no value was sent, use .content_delivery_rules.is_none().

pub fn retention_period(&self) -> Option<&RetentionPeriod>

Optional. How long, in days, versions of dataset contents are kept for the dataset. If not specified or set to null, versions of dataset contents are retained for at most 90 days. The number of versions of dataset contents retained is determined by the versioningConfiguration parameter. For more information, see Keeping Multiple Versions of IoT Analytics datasets in the IoT Analytics User Guide.

pub fn versioning_configuration(&self) -> Option<&VersioningConfiguration>

Optional. How many versions of dataset contents are kept. If not specified or set to null, only the latest version plus the latest succeeded version (if they are different) are kept for the time period specified by the retentionPeriod parameter. For more information, see Keeping Multiple Versions of IoT Analytics datasets in the IoT Analytics User Guide.

pub fn tags(&self) -> &[Tag]

Metadata which can be used to manage the dataset.

If no value was sent for this field, a default will be set. If you want to determine if no value was sent, use .tags.is_none().

pub fn late_data_rules(&self) -> &[LateDataRule]

A list of data rules that send notifications to CloudWatch, when data arrives late. To specify lateDataRules, the dataset must use a DeltaTimer filter.

If no value was sent for this field, a default will be set. If you want to determine if no value was sent, use .late_data_rules.is_none().

impl CreateDatasetInput

pub fn builder() -> CreateDatasetInputBuilder

Creates a new builder-style object to manufacture CreateDatasetInput.

Trait Implementations

impl Clone for CreateDatasetInput

fn clone(&self) -> CreateDatasetInput

Returns a duplicate of the value.

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

Performs copy-assignment from source.

impl Debug for CreateDatasetInput

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

Formats the value using the given formatter.

impl PartialEq for CreateDatasetInput

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

Tests for self and other values to be equal, and is used by ==.

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

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

impl StructuralPartialEq for CreateDatasetInput