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.
|For Gerrit Dashboard: MB-29090|
|124368,15||MB-29090: Differentiate between deleted and expired documents for OnDelete functions||unstable||eventing||Status: MERGED||+2||+1|
|125118,4||MB-29090: Document OnExpiry handler||unstable||eventing||Status: MERGED||+2||+1|