You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is your feature request related to a problem? Please describe.
I would like to be able to replay the messages stored on a persistent queue on subscribe on process start. If my process restarts, I would like the option to replay some or all of the messages on a given topic/queue.
Describe the solution you'd like
Add some sort of replay or start_timestamp kwargs for subscribe that allows replaying messages stored in backend on startup.
Feature code example
To help others understand the proposed feature, illustrate it with a FastStream code example:
fromfaststreamimportFastStreambroker=RedisBroker()
@broker.subscriber(stream="mytopic", replay=True)asyncdefhandle(msg):
# Message is the first message in the redis steamprint(msg)
Describe alternatives you've considered
I thought this would have discussed/implemented given the majority of backends support this functionality (RMQ, redis, nats, kafka), but I can't find anything in the docs or issues.
Additional context
Apologies if I've somehow missed something here!
The text was updated successfully, but these errors were encountered:
Hi! I am sure, that you are able to implement such behavior already by playing with various stream options (last_id at least). I'll try to dig into to help your.
@kumaranvpl you have a bigger expertiece in Redis, can you please take a quick look and decide, should has it sence, should we add new API for it or it is already implemented by some options. Just for backlog
Is your feature request related to a problem? Please describe.
I would like to be able to replay the messages stored on a persistent queue on subscribe on process start. If my process restarts, I would like the option to replay some or all of the messages on a given topic/queue.
Describe the solution you'd like
Add some sort of
replay
orstart_timestamp
kwargs for subscribe that allows replaying messages stored in backend on startup.Feature code example
To help others understand the proposed feature, illustrate it with a FastStream code example:
Describe alternatives you've considered
I thought this would have discussed/implemented given the majority of backends support this functionality (RMQ, redis, nats, kafka), but I can't find anything in the docs or issues.
Additional context
Apologies if I've somehow missed something here!
The text was updated successfully, but these errors were encountered: