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

Message retention time option #49

Open
vitorfox opened this issue Apr 29, 2017 · 7 comments
Open

Message retention time option #49

vitorfox opened this issue Apr 29, 2017 · 7 comments
Assignees

Comments

@vitorfox
Copy link

An option on createQueue and setQueueAttributes methods to set the time a message on a queue will be available to be received.

@smrchy
Copy link
Owner

smrchy commented Jun 16, 2017

You mean a "TTL" (time-to-live) option?

So after like 7 days a message will be deleted?

@vitorfox
Copy link
Author

Exactly 👍

@antoniojtorres
Copy link

I would love this feature as we're looking to move to rsmq from SQS due to costs. Is it feasible at all? or is it not possible due to architecture?

@smrchy
Copy link
Owner

smrchy commented Apr 20, 2019

Hey @antoniojtorres
it sounds like it is possible. I would habe to look into it a bit more and will get back to you. Then i have to find the time to work on it ;)

@smrchy smrchy self-assigned this Apr 20, 2019
@antoniojtorres
Copy link

@smrchy I would be happy to sponsor this feature on behalf of my company if it isn't too complex. I did some digging around and certain data types on redis don't seem to support the standard TTL features. For example bull queue has no ability to support it.

@smrchy
Copy link
Owner

smrchy commented Apr 25, 2019

I am currently working to refactor the RSMQ base away from Coffeescript to Typescript. Once that is done i will add this feature.

@michael-voit
Copy link

@smrchy Is this possible today or any known workarround for a TTL for messages in a queue?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

4 participants