Details
-
Bug
-
Resolution: Fixed
-
Major
-
5.5.0
-
Untriaged
-
Unknown
Description
Ensure document timer events do not fire if the underlying document has been deleted.
While I understand it is feasible to support the ability for doc timers to fire regardless of deletion, doing so is an unnecessary overlap between docTimer and cronTimer.
User should use doc timers when they wish timers follow document lifecycle. If they wish to follow time, and a document is only a context, it should be done via cronTimer.
Attachments
Issue Links
- depends on
-
GOCBC-281 bucket.Get (string, &string) returns error against Vulcan (5.5.0-2036)
- Resolved