#[non_exhaustive]pub struct BatchPutMessageInput {
pub channel_name: Option<String>,
pub messages: Option<Vec<Message>>,
}
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.channel_name: Option<String>
The name of the channel where the messages are sent.
messages: Option<Vec<Message>>
The list of messages to be sent. Each message has the format: { "messageId": "string", "payload": "string"}.
The field names of message payloads (data) that you send to IoT Analytics:
-
Must contain only alphanumeric characters and undescores (_). No other special characters are allowed.
-
Must begin with an alphabetic character or single underscore (_).
-
Cannot contain hyphens (-).
-
In regular expression terms: "^[A-Za-z_]([A-Za-z0-9]*|[A-Za-z0-9][A-Za-z0-9_]*)$".
-
Cannot be more than 255 characters.
-
Are case insensitive. (Fields named foo and FOO in the same payload are considered duplicates.)
For example, {"temp_01": 29} or {"_temp_01": 29} are valid, but {"temp-01": 29}, {"01_temp": 29} or {"__temp_01": 29} are invalid in message payloads.
Implementations§
source§impl BatchPutMessageInput
impl BatchPutMessageInput
sourcepub fn channel_name(&self) -> Option<&str>
pub fn channel_name(&self) -> Option<&str>
The name of the channel where the messages are sent.
sourcepub fn messages(&self) -> &[Message]
pub fn messages(&self) -> &[Message]
The list of messages to be sent. Each message has the format: { "messageId": "string", "payload": "string"}.
The field names of message payloads (data) that you send to IoT Analytics:
-
Must contain only alphanumeric characters and undescores (_). No other special characters are allowed.
-
Must begin with an alphabetic character or single underscore (_).
-
Cannot contain hyphens (-).
-
In regular expression terms: "^[A-Za-z_]([A-Za-z0-9]*|[A-Za-z0-9][A-Za-z0-9_]*)$".
-
Cannot be more than 255 characters.
-
Are case insensitive. (Fields named foo and FOO in the same payload are considered duplicates.)
For example, {"temp_01": 29} or {"_temp_01": 29} are valid, but {"temp-01": 29}, {"01_temp": 29} or {"__temp_01": 29} are invalid in message payloads.
If no value was sent for this field, a default will be set. If you want to determine if no value was sent, use .messages.is_none()
.
source§impl BatchPutMessageInput
impl BatchPutMessageInput
sourcepub fn builder() -> BatchPutMessageInputBuilder
pub fn builder() -> BatchPutMessageInputBuilder
Creates a new builder-style object to manufacture BatchPutMessageInput
.
Trait Implementations§
source§impl Clone for BatchPutMessageInput
impl Clone for BatchPutMessageInput
source§fn clone(&self) -> BatchPutMessageInput
fn clone(&self) -> BatchPutMessageInput
1.0.0 · source§fn clone_from(&mut self, source: &Self)
fn clone_from(&mut self, source: &Self)
source
. Read moresource§impl Debug for BatchPutMessageInput
impl Debug for BatchPutMessageInput
source§impl PartialEq for BatchPutMessageInput
impl PartialEq for BatchPutMessageInput
source§fn eq(&self, other: &BatchPutMessageInput) -> bool
fn eq(&self, other: &BatchPutMessageInput) -> bool
self
and other
values to be equal, and is used
by ==
.