-
Notifications
You must be signed in to change notification settings - Fork 201
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
SQS send-message with message-attributes #435
Comments
Ok I found my answer on a slack archive So you should do something like this: (sqs/send-message {:queue-url a
:message-body "hello world!"
:message-attributes {:attribute-key
{:string-value attribute-value
:data-type "String"
:string-list-values []
:binary-list-values []}}) I don't close this issue as I think the interface between SNS & SQS isn't coherent. (publish :topic-arn "arn:aws:sns:us-east-1:676820690883:my-topic"
:subject "test"
:message (str "Todays is " (java.util.Date.))
:message-attributes {attribute-key attribute-value}) IMO amazonica should allow to do something like this (sqs/send-message {:queue-url a
:message-body "hello world!"
:message-attributes {attribute-key attribute-value}}) as Request objects are comparable https://docs.aws.amazon.com/AWSJavaSDK/latest/javadoc/com/amazonaws/services/sqs/model/SendMessageRequest.html#setMessageAttributes-java.util.Map- |
Top level service functions take clojure data as arguments, the form of which is governed by the recursive conversion of camel case Java objects to hyphenated clojure data. What do you see as inconsistent here between |
They don't coerced the same way. SNS has coercion https://github.com/mcohen01/amazonica/pull/179/files which isn't available in SQS. |
Hi,
I try to send an SQS message with a message-attributes.
I notice there is no coercion like SNS ( #179 )
So my code is:
However I've got this exception:
As there is no documentation nor example on this case,
can you tell me if I miss something or if I have a bad
send-message
usage?Thanks
The text was updated successfully, but these errors were encountered: