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
We have a use case to subscribe to a stream in reverse chronological order from an offset/timestamp. To achieve this on the consumer side we'd need to do lots of in memory caching or multiple requests so ideally Liftbridge could do it for us.
I would plan on it being exposed as a new reverse bool on the SubscribeRequest and a SubscriptionOption in the client library.
Also I think being able to get reverse order would help make cursor fetching more efficient:
We have a use case to subscribe to a stream in reverse chronological order from an offset/timestamp. To achieve this on the consumer side we'd need to do lots of in memory caching or multiple requests so ideally Liftbridge could do it for us.
I would plan on it being exposed as a new
reverse
bool on the SubscribeRequest and a SubscriptionOption in the client library.Also I think being able to get reverse order would help make cursor fetching more efficient:
liftbridge/server/cursors.go
Line 193 in 383469b
I'm happy to have a go at implementing this.
The text was updated successfully, but these errors were encountered: