Struct PutStorageConfigurationOutput 

#[non_exhaustive]
pub struct PutStorageConfigurationOutput {
    pub storage_type: StorageType,
    pub multi_layer_storage: Option<MultiLayerStorage>,
    pub disassociated_data_storage: Option<DisassociatedDataStorageState>,
    pub retention_period: Option<RetentionPeriod>,
    pub configuration_status: Option<ConfigurationStatus>,
    pub warm_tier: Option<WarmTierState>,
    pub warm_tier_retention_period: Option<WarmTierRetentionPeriod>,
    pub disallow_ingest_null_na_n: Option<bool>,
    /* private fields */
}

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.

storage_type: StorageType

The storage tier that you specified for your data. The storageType parameter can be one of the following values:

• SITEWISE_DEFAULT_STORAGE – IoT SiteWise saves your data into the hot tier. The hot tier is a service-managed database.

• MULTI_LAYER_STORAGE – IoT SiteWise saves your data in both the cold tier and the hot tier. The cold tier is a customer-managed Amazon S3 bucket.

multi_layer_storage: Option<MultiLayerStorage>

Contains information about the storage destination.

disassociated_data_storage: Option<DisassociatedDataStorageState>

Contains the storage configuration for time series (data streams) that aren't associated with asset properties. The disassociatedDataStorage can be one of the following values:

• ENABLED – IoT SiteWise accepts time series that aren't associated with asset properties.

  After the disassociatedDataStorage is enabled, you can't disable it.

• DISABLED – IoT SiteWise doesn't accept time series (data streams) that aren't associated with asset properties.

For more information, see Data streams in the IoT SiteWise User Guide.

retention_period: Option<RetentionPeriod>

The number of days your data is kept in the hot tier. By default, your data is kept indefinitely in the hot tier.

configuration_status: Option<ConfigurationStatus>

Contains current status information for the configuration.

warm_tier: Option<WarmTierState>

A service managed storage tier optimized for analytical queries. It stores periodically uploaded, buffered and historical data ingested with the CreaeBulkImportJob API.

warm_tier_retention_period: Option<WarmTierRetentionPeriod>

Set this period to specify how long your data is stored in the warm tier before it is deleted. You can set this only if cold tier is enabled.

disallow_ingest_null_na_n: Option<bool>

Describes the configuration for ingesting NULL and NaN data. By default the feature is allowed. The feature is disallowed if the value is true.

Implementations

impl PutStorageConfigurationOutput

pub fn storage_type(&self) -> &StorageType

The storage tier that you specified for your data. The storageType parameter can be one of the following values:

• SITEWISE_DEFAULT_STORAGE – IoT SiteWise saves your data into the hot tier. The hot tier is a service-managed database.

• MULTI_LAYER_STORAGE – IoT SiteWise saves your data in both the cold tier and the hot tier. The cold tier is a customer-managed Amazon S3 bucket.

pub fn multi_layer_storage(&self) -> Option<&MultiLayerStorage>

Contains information about the storage destination.

pub fn disassociated_data_storage( &self, ) -> Option<&DisassociatedDataStorageState>

Contains the storage configuration for time series (data streams) that aren't associated with asset properties. The disassociatedDataStorage can be one of the following values:

• ENABLED – IoT SiteWise accepts time series that aren't associated with asset properties.

  After the disassociatedDataStorage is enabled, you can't disable it.

• DISABLED – IoT SiteWise doesn't accept time series (data streams) that aren't associated with asset properties.

For more information, see Data streams in the IoT SiteWise User Guide.

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

The number of days your data is kept in the hot tier. By default, your data is kept indefinitely in the hot tier.

pub fn configuration_status(&self) -> Option<&ConfigurationStatus>

Contains current status information for the configuration.

pub fn warm_tier(&self) -> Option<&WarmTierState>

A service managed storage tier optimized for analytical queries. It stores periodically uploaded, buffered and historical data ingested with the CreaeBulkImportJob API.

pub fn warm_tier_retention_period(&self) -> Option<&WarmTierRetentionPeriod>

Set this period to specify how long your data is stored in the warm tier before it is deleted. You can set this only if cold tier is enabled.

pub fn disallow_ingest_null_na_n(&self) -> Option<bool>

Describes the configuration for ingesting NULL and NaN data. By default the feature is allowed. The feature is disallowed if the value is true.

impl PutStorageConfigurationOutput

pub fn builder() -> PutStorageConfigurationOutputBuilder

Creates a new builder-style object to manufacture PutStorageConfigurationOutput.

Trait Implementations

impl Clone for PutStorageConfigurationOutput

fn clone(&self) -> PutStorageConfigurationOutput

Returns a duplicate of the value.

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

Performs copy-assignment from source.

impl Debug for PutStorageConfigurationOutput

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

Formats the value using the given formatter.

impl PartialEq for PutStorageConfigurationOutput

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

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

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 RequestId for PutStorageConfigurationOutput

fn request_id(&self) -> Option<&str>

Returns the request ID, or None if the service could not be reached.

impl StructuralPartialEq for PutStorageConfigurationOutput