SQS - Message Attributes

[patilarpith]

Unable to fetch SentTimestamp message attribute.

ReceiveMessageRequest class functions like GetAttributeNames() & SetAttributeNames() deals with QueueAttributeName.

How to set ReceiveMessageRequest to also fetch SentTimestamp during a ReceiveMessage() request?

[patilarpith]

@JonathanHenson Could you please take a look at this?

[JonathanHenson]

I think you need GetMessageAttributes() and SetMessageAttributes() on the Message class for the Result and then

ReceiveMessageRequest you should use GetMessageAttributeNames() and SetMessageAttributeNames()

[patilarpith]

@JonathanHenson Here is my confusion

SQS: Message.h has method

inline const Aws::Map<QueueAttributeName, Aws::String>& GetAttributes()

Here is the description of this method

<p><code>SenderId</code>, <code>SentTimestamp</code>, <code>ApproximateReceiveCount</code>, and/or <code>ApproximateFirstReceiveTimestamp</code>. <code>SentTimestamp</code> and <code>ApproximateFirstReceiveTimestamp</code> are each returned as an integer representing the <a href="http://en.wikipedia.org/wiki/Unix_time">epoch time</a> in milliseconds.</p>

This is the QueueAttributeName enum

  enum class QueueAttributeName
  {
    NOT_SET,
    Policy,
    VisibilityTimeout,
    MaximumMessageSize,
    MessageRetentionPeriod,
    ApproximateNumberOfMessages,
    ApproximateNumberOfMessagesNotVisible,
    CreatedTimestamp,
    LastModifiedTimestamp,
    QueueArn,
    ApproximateNumberOfMessagesDelayed,
    DelaySeconds,
    ReceiveMessageWaitTimeSeconds,
    RedrivePolicy
  };

It looks like SetMessageAttributeNames() of ReceiveMessageRequest class deals with custom message attributes that can be added to SQS Messages.

It is still unclear how to fetch SentTimestamp attribute along with the SQS Message

[JonathanHenson]

I think the documentation is probably wrong. Try setting SentTimestamp on message attributes and Getting it back out of the message attributes. I'll check around here today to confirm.

[patilarpith]

Yes that would be one solution but I don't have access to the en-queuing service. Thanks for the assistance.

[JonathanHenson]

I'm slightly confused. Did that work? Is your issue resolved?

[patilarpith]

No it didn't solve my problem but what you suggested is a possible work-around. If I had access to the en-queuing service then I could have went ahead with this solution

[JonathanHenson]

What type of access do you need? Do you know how to use the sdk to do this?
Are you referring to documentation? Or support with the internal aws team?

Is there some way I can help? If this solves your problem, I will notify
the relevant teams that their documentation is out of date.
On Feb 2, 2016 1:23 AM, "Patil Arpith" notifications@github.com wrote:

No it didn't solve my problem but what you suggested is a possible
work-around. If I had access to the en-queuing service then I could have
went ahead with this solution

—
Reply to this email directly or view it on GitHub
#83 (comment).

[patilarpith]

We use SQS internally for processing a bunch of jobs asynchronously. What I meant by not having access to the en-queuing service is that; I don't have access to the service that en-queues the jobs to be processed.

I want to understand how to fetch SentTimestamp on the de-queuing end using aws cpp sdk. Up until now I used to do this using the SQS REST API

[JonathanHenson]

Im assuming you mean "Http" api since SQS isn't restful. Are you certain
you were pulling this out of Attributes and not MessageAttributes? If so,
we can work on fixing this for you ASAP. I need to confirm the behavior
with the SQS team, but the update to the enum is very straight forward
(it's just an update to the json model for the service).
On Feb 2, 2016 1:43 AM, "Patil Arpith" notifications@github.com wrote:

We use SQS internally for processing a bunch of jobs asynchronously. What
I meant by not having access to the en-queuing service is that; I don't
have access to the service that en-queues the jobs to be processed.

I want to understand how to fetch SentTimestamp on the de-queuing end
using aws cpp sdk. Up until now I used to do this using the SQS REST API

—
Reply to this email directly or view it on GitHub
#83 (comment).

[patilarpith]

Yes I can confirm this. Here is a piece of code from (forked and then self maintained) library which does sqs_get_message() over HTTP API

[patilarpith]

Checking in on this

[patilarpith]

@JonathanHenson Did you get a chance to look at this?

[Bu11etmagnet]

Currently there is no enum value named SentTimestamp. I did a

$ find aws-cpp-sdk-* -name *.h | xargs grep -wn SentTimestamp

and every hit was from a comment, in sqs/model/ReceiveMessageRequest.h or sqs/model/Message.h

I think using QueueAttributeName for ReceiveMessage is wrong. There should be a separate enum, because the set of attributes that can be requested from ReceiveMessage is different from the set of attributes used by GetQueueAttributes/SetQueueAttributes.

Alternatively, the extra attributes could be added to QueueAttributeName (but the name would be misleading).

[prestomation]

Hi,
Message Attributes don't seem to be modeled.

I think this will work but I have not tested.
When you received the message:
receiveMessageRequest.AddMessageAttributeNames("SentTimestamp");
//Now send your request and retrieve your result.
auto sentTimeStamp = receiveMessageResult.GetMessages()[0].GetMessageAttributes()["SentTimestamp]";

The SQS integration tests send and later read some custom message attributes here: https://github.com/aws/aws-sdk-cpp/blob/master/aws-cpp-sdk-sqs-integration-tests/QueueOperationTest.cpp#L259