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.
When a new timeline is created for an event type Nakadi sets the 'clean at' date for the previous timeline based on the event type retention time. After the retention period is over Nakadi deletes the old topic.
But if the event type's retention time is set to -1 the old topic is removed almost immediately because of the way the cleantAt date is calculated:
In our setup we use -1 for indefinite retention, although it is not described in Nakadi docs. So either Nakadi should not allow -1 for retention time or clean up should not happen.
The text was updated successfully, but these errors were encountered:
Yeah, that why we start using it. But is it to be officially supported by Nakadi? Taking into account it's future support for other messaging backends and other features like timelines.
Yeah, that why we start using it. But is it to be officially supported by Nakadi? Taking into account it's future support for other messaging backends and other features like timelines.
it is gonna be discussed internally (I will update on that soon), from my point of view it makes, because kafka supports it.
When a new timeline is created for an event type Nakadi sets the 'clean at' date for the previous timeline based on the event type retention time. After the retention period is over Nakadi deletes the old topic.
But if the event type's retention time is set to -1 the old topic is removed almost immediately because of the way the cleantAt date is calculated:
nakadi/src/main/java/org/zalando/nakadi/service/timeline/TimelineService.java
Line 341 in 96a6967
In our setup we use -1 for indefinite retention, although it is not described in Nakadi docs. So either Nakadi should not allow -1 for retention time or clean up should not happen.
The text was updated successfully, but these errors were encountered: