Details
-
Improvement
-
Resolution: Done
-
Major - P3
-
None
-
None
-
None
Description
The following question came up as part of a scoping discussion for the upcoming Notification API feature:
Do drivers need to do anything special to understand that the cursors coming
|
back from change notification aggregations are tailable?
|
Specifically: while it's important for us to distinguish a cursor's type when sending a request to the server, is it important to track that information after the cursor has been created? Are there cases where it is not good enough simply to track the presence of a non-zero cursor id on subsequent server replies?
The question arises from the fact that a TAILABLE_AWAIT cursor will be implicitly created by the addition of the new `$changeNotification` stage in an agg query, which drivers will need to accommodate as such. It is unclear whether the server should return some flag in the first response, giving the drivers a hint as to what type of cursor to create, or if we can just track the cursor id.