Message attribute list values in SendMessageBatch operation are not supported. (Aws::SQS::Errors::UnsupportedOperation)

[rsosag]

Hi community, I need help with this error I'm getting when I try to use client.send_message_batch
Message attribute list values in SendMessageBatch operation are not supported. (Aws::SQS::Errors::UnsupportedOperation)

Failure with this payload 👇🏼

resp = client.send_message_batch({
  queue_url: "String", 
  entries: [
    {
      id: "String", # required
      message_body: "String", # required
      message_attributes: {
        "String" => {
          string_value: "String",
          string_list_values: [],
          binary_list_values: [],
          data_type: "String"
        },
      },
      message_deduplication_id: "String",
      message_group_id: "String",
    },
  ],
})

Works successfully with this payload 👇🏼

resp = client.send_message_batch({
  queue_url: "String", 
  entries: [
    {
      id: "String", # required
      message_body: "String", # required
      message_attributes: {
        "String" => {
          string_value: "String",
          data_type: "String"
        },
      },
      message_deduplication_id: "String",
      message_group_id: "String",
    },
  ],
})

The difference I see is in message_attributes with string_list_values: [] and binary_list_values: [], which are not yet implemented in AWS::SQS, but I get these after using client.receive_message 👇🏼

messages = client.receive_message(
  queue_url: url,
  max_number_of_messages: batch_size,
  attribute_names: ['All'],
  message_attribute_names: ['All']
).messages

Any ideas or solutions you can suggest to me? 🙏🏼

[RanVaknin]

Hi @rsosag ,

Thanks for reaching out.

Looking at the API docs for SQS, these two fields are explicitly documented as not implemented:

StringListValues

Not implemented. Reserved for future use.

Type: Array of strings

Required: No

BinaryListValues

Not implemented. Reserved for future use.

Type: Array of Base64-encoded binary data objects

Required: No

I'm not sure why this was released without being implemented, but from an SDK perspective we cannot add /remove fields as the SDK is code-generated directly from the API model of the various AWS services. You should not use these fields until they are documented as implemented by the SQS service.

Thanks,
Ran~

[rsosag]

@RanVaknin thanks you

[github-actions[bot]]

Hello! Reopening this discussion to make it searchable.