Struct BatchPutMessageInput 

#[non_exhaustive]
pub struct BatchPutMessageInput {
    pub channel_name: Option<String>,
    pub messages: Option<Vec<Message>>,
}

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.

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

impl BatchPutMessageInput

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

The name of the channel where the messages are sent.

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().

impl BatchPutMessageInput

pub fn builder() -> BatchPutMessageInputBuilder

Creates a new builder-style object to manufacture BatchPutMessageInput.

Trait Implementations

impl Clone for BatchPutMessageInput

fn clone(&self) -> BatchPutMessageInput

Returns a duplicate of the value.

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

Performs copy-assignment from source.

impl Debug for BatchPutMessageInput

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

Formats the value using the given formatter.

impl PartialEq for BatchPutMessageInput

fn eq(&self, other: &BatchPutMessageInput) -> 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 StructuralPartialEq for BatchPutMessageInput