Skip to content
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

Question: How do I manually Ack a message in dotnet core? #151

Open
kentonbmax opened this issue Feb 16, 2021 · 3 comments
Open

Question: How do I manually Ack a message in dotnet core? #151

kentonbmax opened this issue Feb 16, 2021 · 3 comments
Labels
enhancement New feature or request
Milestone

Comments

@kentonbmax
Copy link

User Case: an EF error/timeout occurs while executing my function. Any other error occurs, I do not want to loose the message. Therefore I want to only manually Ack messages that have been successfully processed.

@yojagad yojagad added enhancement New feature or request and removed Needs: Triage (Functions) labels Feb 25, 2021
@yojagad
Copy link
Contributor

yojagad commented Feb 25, 2021

Needs some design exploration. Probably needs an approach similar to service bus where customers can specify messageHandlingOptions like below

{
  "version": "2.0",
  "extensions": {
    "rabbitMq": {
      "messageHandlerOptions": {
        "autoComplete": false
      }
    }
  }
}

@yojagad yojagad added this to the Triaged milestone Feb 25, 2021
@dr-consit
Copy link

This seems like a "must have" feature.
Queue handling without the possibility of abandoned messages with re-sends, doesn't really seem like queue handling. More sort of like "spray and pray" IMHO.

@steveb85
Copy link

did this ever get worked on?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

4 participants