llazanja opened a new issue, #759:
URL: https://github.com/apache/pekko-connectors/issues/759

   Hi, in library `peko-connectors-sqs-1.x.x`, `delaySeconds` is a property 
which can be specified on each individual message request 
(`SendMessageRequest`). However, when these requests are mapped to 
`SendMessageBatchRequestEntry`, property `delaySeconds` is left out (check 
[SqsPublishFlow 
code](https://github.com/apache/pekko-connectors/blob/main/sqs/src/main/scala/org/apache/pekko/stream/connectors/sqs/scaladsl/SqsPublishFlow.scala#L89-L96)).
   
   Is there a workaround for this, or do you think I should raise a pull 
request with the missing mapping?
   
   Code snippets:
   
   message request
   ```        
   SendMessageRequest
       .builder()
       .queueUrl(queueUrl)
       .delaySeconds(delaySeconds)
       .messageBody(rawJson)
       .messageAttributes(attributeMap.asJava)
       .build()
   ```
   batch request entry mapping
   ```
       Flow[Iterable[SendMessageRequest]]
         .map { requests =>
           val entries = requests.zipWithIndex.map {
             case (r, i) =>
               SendMessageBatchRequestEntry
                 .builder()
                 .id(i.toString)
                 .messageBody(r.messageBody())
                 .messageAttributes(r.messageAttributes())
                 .messageGroupId(r.messageGroupId())
                 .messageDeduplicationId(r.messageDeduplicationId())
             // NOTE: missing mapping for delaySeconds
                 .build()
           }
   ```
   
   
   Impact:
   It is not possible to specify individual delay on an sqs message, while AWS 
supports this functionality (check example 2 on the [documentation 
page](https://docs.aws.amazon.com/AWSSimpleQueueService/latest/APIReference/API_SendMessageBatch.html#API_SendMessageBatch_Examples)).
   
   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]


---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to