-
Type: Bug
-
Resolution: Won't Do
-
Priority: Major - P3
-
Affects Version/s: None
-
Component/s: manual
-
Labels:None
-
0.3
https://docs.mongodb.com/manual/core/tailable-cursors/#tailable-cursors
The behavior leading to an invalid cursor seems to involve calling cursor.next() after the last document returned from the cursor has already rolled off a capped collection. We should confirm this is the correct interpretation and update the language as appropriate.
Original Description
the cursor returns the document at the “end” of the collection and then the application deletes that document.
An application cannot delete a document from a capped collection. Is this referring to a case where the document is question is overwritten when the capped collection rolls over?