Uploaded image for project: 'Couchbase Server'
  1. Couchbase Server
  2. MB-38730

[BP MB-29090] - Differentiate between Delete vs Expiry in OnDelete()

    XMLWordPrintable

Details

    • Improvement
    • Status: Closed
    • Major
    • Resolution: Fixed
    • 5.5.0, 6.0.4, 6.5.1
    • 6.6.0
    • eventing

    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

          No reviews matched the request. Check your Options in the drop-down menu of this sections header.

          Activity

            There are no commits yet on this issue.

            People

              ankit.prabhu Ankit Prabhu
              jeelan.poola Jeelan Poola
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved:

                Gerrit Reviews

                  There are no open Gerrit changes

                  PagerDuty