[DOCS-10146] cursor id of aggregate reply not set Created: 29/Mar/17 Updated: 30/Oct/23 |
|
| Status: | Closed |
| Project: | Documentation |
| Component/s: | manual, Server |
| Affects Version/s: | None |
| Fix Version/s: | Server_Docs_20231030 |
| Type: | Improvement | Priority: | Major - P3 |
| Reporter: | Cen Li | Assignee: | Unassigned |
| Resolution: | Won't Do | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Participants: | |
| Days since reply: | 1 year, 14 weeks, 2 days ago |
| Epic Link: | DOCSP-1769 |
| Description |
| Comments |
| Comment by Education Bot [ 31/Oct/22 ] |
|
Hello! This ticket has been closed due to inactivity. If you believe this ticket is still important, please reopen it and leave a comment to explain why. Thank you! |
| Comment by Cen Li [ 27/Apr/17 ] |
|
Hi Thomas, Thx for your clarification. Brs, |
| Comment by Kelsey Schubert [ 19/Apr/17 ] |
|
Hi licen, Sorry for the delay getting back to you. For non-legacy opqueries, we use the wire protocol slightly differently, and include the cursor id within the documents field as shown in your description. This behavior is expected by MongoDB drivers. For example, in PyMongo, you can review the source code: https://github.com/mongodb/mongo-python-driver/blob/3.4.0/pymongo/collection.py#L1876-L1886 I've moved this ticket to the DOCS project as an improvement request to clarify the wire protocol in our documentation. Thank you, |