The maxAwaitTimeMS option is broken for change streams and is not properly implemented for find options. It doesn't exist at all for aggregate options which needs to support maxAwaitTimeMS since $changeStream returns a tailableawait cursor.
The current cursor implementation needs to be augmented with the ability to take a maxAwaitTime parameter, and that parameter needs to be sent on getMore requests when set. Additionally, the OptMaxAwaitTime option should implement the AggregateOptioner interface. Finally, when the Watch or a find or aggregate method receives an OptMaxAwaitTIme, it should not send it on the initial request and instead hold it and use that value when creating the cursor.
- depends on
-
GODRIVER-272 Implement redesigned options for the Collection methods
- Closed
- related to
-
GODRIVER-146 Add option maxAwaitTimeMS on getMore commands
- Closed