#[non_exhaustive]pub struct Datastore {
pub name: Option<String>,
pub storage: Option<DatastoreStorage>,
pub arn: Option<String>,
pub status: Option<DatastoreStatus>,
pub retention_period: Option<RetentionPeriod>,
pub creation_time: Option<DateTime>,
pub last_update_time: Option<DateTime>,
pub last_message_arrival_time: Option<DateTime>,
pub file_format_configuration: Option<FileFormatConfiguration>,
pub datastore_partitions: Option<DatastorePartitions>,
}
Expand description
Information about a data store.
Fields (Non-exhaustive)§
This struct is marked as non-exhaustive
Struct { .. }
syntax; cannot be matched against without a wildcard ..
; and struct update syntax will not work.name: Option<String>
The name of the data store.
storage: Option<DatastoreStorage>
Where data in a data store is stored.. You can choose serviceManagedS3
storage, customerManagedS3
storage, or iotSiteWiseMultiLayerStorage
storage. The default is serviceManagedS3
. You can't change the choice of Amazon S3 storage after your data store is created.
arn: Option<String>
The ARN of the data store.
status: Option<DatastoreStatus>
The status of a data store:
- CREATING
-
The data store is being created.
- ACTIVE
-
The data store has been created and can be used.
- DELETING
-
The data store is being deleted.
retention_period: Option<RetentionPeriod>
How long, in days, message data is kept for the data store. When customerManagedS3
storage is selected, this parameter is ignored.
creation_time: Option<DateTime>
When the data store was created.
last_update_time: Option<DateTime>
The last time the data store was updated.
last_message_arrival_time: Option<DateTime>
The last time when a new message arrived in the data store.
IoT Analytics updates this value at most once per minute for Amazon Simple Storage Service one data store. Hence, the lastMessageArrivalTime
value is an approximation.
This feature only applies to messages that arrived in the data store after October 23, 2020.
file_format_configuration: Option<FileFormatConfiguration>
Contains the configuration information of file formats. IoT Analytics data stores support JSON and Parquet.
The default file format is JSON. You can specify only one format.
You can't change the file format after you create the data store.
datastore_partitions: Option<DatastorePartitions>
Contains information about the partition dimensions in a data store.
Implementations§
Source§impl Datastore
impl Datastore
Sourcepub fn storage(&self) -> Option<&DatastoreStorage>
pub fn storage(&self) -> Option<&DatastoreStorage>
Where data in a data store is stored.. You can choose serviceManagedS3
storage, customerManagedS3
storage, or iotSiteWiseMultiLayerStorage
storage. The default is serviceManagedS3
. You can't change the choice of Amazon S3 storage after your data store is created.
Sourcepub fn status(&self) -> Option<&DatastoreStatus>
pub fn status(&self) -> Option<&DatastoreStatus>
The status of a data store:
- CREATING
-
The data store is being created.
- ACTIVE
-
The data store has been created and can be used.
- DELETING
-
The data store is being deleted.
Sourcepub fn retention_period(&self) -> Option<&RetentionPeriod>
pub fn retention_period(&self) -> Option<&RetentionPeriod>
How long, in days, message data is kept for the data store. When customerManagedS3
storage is selected, this parameter is ignored.
Sourcepub fn creation_time(&self) -> Option<&DateTime>
pub fn creation_time(&self) -> Option<&DateTime>
When the data store was created.
Sourcepub fn last_update_time(&self) -> Option<&DateTime>
pub fn last_update_time(&self) -> Option<&DateTime>
The last time the data store was updated.
Sourcepub fn last_message_arrival_time(&self) -> Option<&DateTime>
pub fn last_message_arrival_time(&self) -> Option<&DateTime>
The last time when a new message arrived in the data store.
IoT Analytics updates this value at most once per minute for Amazon Simple Storage Service one data store. Hence, the lastMessageArrivalTime
value is an approximation.
This feature only applies to messages that arrived in the data store after October 23, 2020.
Sourcepub fn file_format_configuration(&self) -> Option<&FileFormatConfiguration>
pub fn file_format_configuration(&self) -> Option<&FileFormatConfiguration>
Contains the configuration information of file formats. IoT Analytics data stores support JSON and Parquet.
The default file format is JSON. You can specify only one format.
You can't change the file format after you create the data store.
Sourcepub fn datastore_partitions(&self) -> Option<&DatastorePartitions>
pub fn datastore_partitions(&self) -> Option<&DatastorePartitions>
Contains information about the partition dimensions in a data store.
Trait Implementations§
impl StructuralPartialEq for Datastore
Auto Trait Implementations§
impl Freeze for Datastore
impl RefUnwindSafe for Datastore
impl Send for Datastore
impl Sync for Datastore
impl Unpin for Datastore
impl UnwindSafe for Datastore
Blanket Implementations§
Source§impl<T> BorrowMut<T> for Twhere
T: ?Sized,
impl<T> BorrowMut<T> for Twhere
T: ?Sized,
Source§fn borrow_mut(&mut self) -> &mut T
fn borrow_mut(&mut self) -> &mut T
Source§impl<T> CloneToUninit for Twhere
T: Clone,
impl<T> CloneToUninit for Twhere
T: Clone,
Source§impl<T> Instrument for T
impl<T> Instrument for T
Source§fn instrument(self, span: Span) -> Instrumented<Self>
fn instrument(self, span: Span) -> Instrumented<Self>
Source§fn in_current_span(self) -> Instrumented<Self>
fn in_current_span(self) -> Instrumented<Self>
Source§impl<T> IntoEither for T
impl<T> IntoEither for T
Source§fn into_either(self, into_left: bool) -> Either<Self, Self>
fn into_either(self, into_left: bool) -> Either<Self, Self>
self
into a Left
variant of Either<Self, Self>
if into_left
is true
.
Converts self
into a Right
variant of Either<Self, Self>
otherwise. Read moreSource§fn into_either_with<F>(self, into_left: F) -> Either<Self, Self>
fn into_either_with<F>(self, into_left: F) -> Either<Self, Self>
self
into a Left
variant of Either<Self, Self>
if into_left(&self)
returns true
.
Converts self
into a Right
variant of Either<Self, Self>
otherwise. Read moreSource§impl<T> Paint for Twhere
T: ?Sized,
impl<T> Paint for Twhere
T: ?Sized,
Source§fn fg(&self, value: Color) -> Painted<&T>
fn fg(&self, value: Color) -> Painted<&T>
Returns a styled value derived from self
with the foreground set to
value
.
This method should be used rarely. Instead, prefer to use color-specific
builder methods like red()
and
green()
, which have the same functionality but are
pithier.
§Example
Set foreground color to white using fg()
:
use yansi::{Paint, Color};
painted.fg(Color::White);
Set foreground color to white using white()
.
use yansi::Paint;
painted.white();
Source§fn bright_black(&self) -> Painted<&T>
fn bright_black(&self) -> Painted<&T>
Source§fn bright_red(&self) -> Painted<&T>
fn bright_red(&self) -> Painted<&T>
Source§fn bright_green(&self) -> Painted<&T>
fn bright_green(&self) -> Painted<&T>
Source§fn bright_yellow(&self) -> Painted<&T>
fn bright_yellow(&self) -> Painted<&T>
Source§fn bright_blue(&self) -> Painted<&T>
fn bright_blue(&self) -> Painted<&T>
Source§fn bright_magenta(&self) -> Painted<&T>
fn bright_magenta(&self) -> Painted<&T>
Source§fn bright_cyan(&self) -> Painted<&T>
fn bright_cyan(&self) -> Painted<&T>
Source§fn bright_white(&self) -> Painted<&T>
fn bright_white(&self) -> Painted<&T>
Source§fn bg(&self, value: Color) -> Painted<&T>
fn bg(&self, value: Color) -> Painted<&T>
Returns a styled value derived from self
with the background set to
value
.
This method should be used rarely. Instead, prefer to use color-specific
builder methods like on_red()
and
on_green()
, which have the same functionality but
are pithier.
§Example
Set background color to red using fg()
:
use yansi::{Paint, Color};
painted.bg(Color::Red);
Set background color to red using on_red()
.
use yansi::Paint;
painted.on_red();
Source§fn on_primary(&self) -> Painted<&T>
fn on_primary(&self) -> Painted<&T>
Source§fn on_magenta(&self) -> Painted<&T>
fn on_magenta(&self) -> Painted<&T>
Source§fn on_bright_black(&self) -> Painted<&T>
fn on_bright_black(&self) -> Painted<&T>
Source§fn on_bright_red(&self) -> Painted<&T>
fn on_bright_red(&self) -> Painted<&T>
Source§fn on_bright_green(&self) -> Painted<&T>
fn on_bright_green(&self) -> Painted<&T>
Source§fn on_bright_yellow(&self) -> Painted<&T>
fn on_bright_yellow(&self) -> Painted<&T>
Source§fn on_bright_blue(&self) -> Painted<&T>
fn on_bright_blue(&self) -> Painted<&T>
Source§fn on_bright_magenta(&self) -> Painted<&T>
fn on_bright_magenta(&self) -> Painted<&T>
Source§fn on_bright_cyan(&self) -> Painted<&T>
fn on_bright_cyan(&self) -> Painted<&T>
Source§fn on_bright_white(&self) -> Painted<&T>
fn on_bright_white(&self) -> Painted<&T>
Source§fn attr(&self, value: Attribute) -> Painted<&T>
fn attr(&self, value: Attribute) -> Painted<&T>
Enables the styling Attribute
value
.
This method should be used rarely. Instead, prefer to use
attribute-specific builder methods like bold()
and
underline()
, which have the same functionality
but are pithier.
§Example
Make text bold using attr()
:
use yansi::{Paint, Attribute};
painted.attr(Attribute::Bold);
Make text bold using using bold()
.
use yansi::Paint;
painted.bold();
Source§fn rapid_blink(&self) -> Painted<&T>
fn rapid_blink(&self) -> Painted<&T>
Source§fn quirk(&self, value: Quirk) -> Painted<&T>
fn quirk(&self, value: Quirk) -> Painted<&T>
Enables the yansi
Quirk
value
.
This method should be used rarely. Instead, prefer to use quirk-specific
builder methods like mask()
and
wrap()
, which have the same functionality but are
pithier.
§Example
Enable wrapping using .quirk()
:
use yansi::{Paint, Quirk};
painted.quirk(Quirk::Wrap);
Enable wrapping using wrap()
.
use yansi::Paint;
painted.wrap();
Source§fn clear(&self) -> Painted<&T>
👎Deprecated since 1.0.1: renamed to resetting()
due to conflicts with Vec::clear()
.
The clear()
method will be removed in a future release.
fn clear(&self) -> Painted<&T>
resetting()
due to conflicts with Vec::clear()
.
The clear()
method will be removed in a future release.Source§fn whenever(&self, value: Condition) -> Painted<&T>
fn whenever(&self, value: Condition) -> Painted<&T>
Conditionally enable styling based on whether the Condition
value
applies. Replaces any previous condition.
See the crate level docs for more details.
§Example
Enable styling painted
only when both stdout
and stderr
are TTYs:
use yansi::{Paint, Condition};
painted.red().on_yellow().whenever(Condition::STDOUTERR_ARE_TTY);