You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@camel.apache.org by "Claus Ibsen (JIRA)" <ji...@apache.org> on 2013/10/11 15:26:42 UTC

[jira] [Resolved] (CAMEL-6850) Allow AWS SQS to not ack or even if it doesn't encounter an exception

     [ https://issues.apache.org/jira/browse/CAMEL-6850?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Claus Ibsen resolved CAMEL-6850.
--------------------------------

    Resolution: Fixed

> Allow AWS SQS to not ack or even if it doesn't encounter an exception
> ---------------------------------------------------------------------
>
>                 Key: CAMEL-6850
>                 URL: https://issues.apache.org/jira/browse/CAMEL-6850
>             Project: Camel
>          Issue Type: Improvement
>          Components: camel-aws
>    Affects Versions: 2.12.1
>            Reporter: Christian Posta
>            Assignee: Christian Posta
>             Fix For: 2.12.2, 2.13.0
>
>         Attachments: CAMEL-6850-update1.patch
>
>
> Since SQS doesn't allow selectors it could be nice to use camel's filtering and ignore messages that don't fit through that filter. Right now DeleteMessage is sent back onCompletion. Proposed is to set a header of some other facility to let the onCompletion know that even though there wasn't a failure, still don't send back the ack/delete message. I'll work on a patch.



--
This message was sent by Atlassian JIRA
(v6.1#6144)