Details
-
Improvement
-
Resolution: Fixed
-
Major
-
5.5.0, 6.0.4, 6.5.1
Description
Due to MB-26907, the only way by which a user can create a system that alerts them on a document's expiry is by creating a timer at the expiration time(meta.expiration) or before that.
Why we need an OnExpiry Handler:
- This mechanism (using Timers) is not elegant and we should it make it easy for the user to consume Expiry events.
- Timers impose a overhead of managing it using local storage(plasma or buckets) there by affecting sizing guidelines.
- Timer's execution is not guaranteed at the specified time if the load on the system is high & the eventing nodes are under provisioned.
This is a tracking bug to implement an OnExpiry handler once MB-26907 implements a system by which DCP consumers can differentiate between Delete and Expiry.
Attachments
Issue Links
- Clones
-
MB-29090 Differentiate between Delete vs Expiry in OnDelete()
- Closed
- depends on
-
MB-26907 DCP: Differentiate Between Delete and Expiry Operations
- Closed
- is a backport of
-
MB-29090 Differentiate between Delete vs Expiry in OnDelete()
- Closed
- is triggering
-
DOC-6680 Document OnExpiry handler
- Resolved
- mentioned in
-
Page Loading...
For Gerrit Dashboard: MB-38730 | ||||||
---|---|---|---|---|---|---|
# | Subject | Branch | Project | Status | CR | V |
126691,4 | MB-38730: Fix ci functional test | mad-hatter | eventing | Status: MERGED | +2 | +1 |
126761,2 | MB-38730: Differentiate between deleted and expired documents for OnDelete functions | mad-hatter | eventing | Status: MERGED | +2 | +1 |