[DOCS-12744] [Server] Delete outdated statements on batchSize page Created: 22/May/19 Updated: 30/Oct/23 Resolved: 21/Apr/23 |
|
| Status: | Closed |
| Project: | Documentation |
| Component/s: | Server |
| Affects Version/s: | None |
| Fix Version/s: | Server_Docs_20231030 |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Tess Avitabile (Inactive) | Assignee: | Alison Huh |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | quick-win, reopened | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Participants: | |
| Days since reply: | 1 year, 14 weeks, 1 day ago |
| Description |
DescriptionThe page on batchSize states "Do not use a batch size of 1." and "Specifying 1 or a negative number is analogous to using the limit() method." However, this is no longer true. Today, batchSize:1 behaves the same as any other positive batchSize. It does not imply a limit of 1:
And we can see that documents are returned 1 at a time:
Scope of changesImpact to Other DocsMVP (Work and Date)Resources (Scope or Design Docs, Invision, etc.) |
| Comments |
| Comment by Sarah Olson [ 01/Nov/22 ] | ||||
|
Thanks for the confirm david.storch@mongodb.com. We'll leave it open!
| ||||
| Comment by David Storch [ 01/Nov/22 ] | ||||
|
Hi sarah.olson@mongodb.com ashley.brown@mongodb.com, I actually think this is still a problem that we should fix, so I've re-opened this ticket. The docs say two conflicting things right now:
And:
I don't think either statement is correct. batchSize 1 just acts like a normal batch size these days. I did double check using mongosh that this is true. Here's an example:
I think we can safely just delete the incorrect information about batchSize:1. | ||||
| 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 David Storch [ 23/May/19 ] | ||||
|
Good catch tess.avitabile! | ||||
| Comment by Tess Avitabile (Inactive) [ 22/May/19 ] | ||||
|
CC david.storch |