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
{{ message }}
This repository has been archived by the owner on Jun 7, 2024. It is now read-only.
Is it already possible (without actually consuming the last message in the nakadi stream and checking it) to check the last occured_at or the last received_at of a partition with an endpoint? we are analyzing the nakadi stream, and to check if we got all the latest events we would also need the last occured_at. this should be easily integratable with https://github.com/zalando-zmon and i would like to avoid subscriptions all the time for it.
just getting the last message with the low level api would be easier (i don't have to create a subscription), but i would avoid using this too for deprecation reasons.
this could also be extend to just get the last message of a partition, so other usecase could be covered as well ...
The text was updated successfully, but these errors were encountered:
Sorry for the long delay in getting back to you. Currently it is not possible, but that sounds interesting. We'll try to include it in our backlog, but of course, PRs are always welcome :)
Is it already possible (without actually consuming the last message in the nakadi stream and checking it) to check the last occured_at or the last received_at of a partition with an endpoint? we are analyzing the nakadi stream, and to check if we got all the latest events we would also need the last occured_at. this should be easily integratable with https://github.com/zalando-zmon and i would like to avoid subscriptions all the time for it.
just getting the last message with the low level api would be easier (i don't have to create a subscription), but i would avoid using this too for deprecation reasons.
this could also be extend to just get the last message of a partition, so other usecase could be covered as well ...
The text was updated successfully, but these errors were encountered: