camel-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Andy Redhead (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CAMEL-7591) AWS SQS Delete Message Endpoint
Date Fri, 11 Jul 2014 08:02:06 GMT

    [ https://issues.apache.org/jira/browse/CAMEL-7591?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14058533#comment-14058533
] 

Andy Redhead commented on CAMEL-7591:
-------------------------------------

If you don't delete the message, the queue will make a non-deleted message visible to consumers
after a certain amount of time, which will allow it to be re-consumed.

Explicitly deleting the message off the queue once it has been successfully processed prevents
"pointless" re-delivery and processing.

> AWS SQS Delete Message Endpoint
> -------------------------------
>
>                 Key: CAMEL-7591
>                 URL: https://issues.apache.org/jira/browse/CAMEL-7591
>             Project: Camel
>          Issue Type: Improvement
>            Reporter: Andy Redhead
>
> It would be useful to be able to send a "delete" message to SQS for a message that was
read from SQS earlier in a route (rather than leaving the original consumer to delete it).
> This is particularly useful when the consumer is sending "inOnly" (and has the "do not
delete message" attribute set. This allows the point where the message is deleted from the
incoming queue to be dictated by the route.
> To try and get the best throughput from SQS, there should be an option to batch multiple
delete messages into a single SQS request.
> Cheers, Andy



--
This message was sent by Atlassian JIRA
(v6.2#6252)

Mime
View raw message