-
-
Notifications
You must be signed in to change notification settings - Fork 111
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
Support history
#7
Comments
kafka has offsets so it should be possible, also for time it has offsets_for_times which returns the offset inside that timestamp. It's a bit tricky because of the kafka partitions, but I'll investigate further. And redis stream have xrange but not sure if they support datetime. Another thing to think about is how to retrieve everything. Let's say you have a topic where the content expires daily "notifications", so you want to read it all, how would it look like? |
Something that'd be really valuable would be to allow subscriptions to start up with some initial history.
For example:
Not all backends will support this, but Redis Streams, and Apache Kafka do. I think the implementation may be a bit fiddly to get right, but before we even get there let's discuss the API.
One option here might be...
The text was updated successfully, but these errors were encountered: