[SERVER-39852] Collections incorrectly shown as empty in shell Created: 26/Feb/19 Updated: 29/Oct/23 Resolved: 29/Mar/19 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Shell |
| Affects Version/s: | None |
| Fix Version/s: | 4.1.10 |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | David Golub | Assignee: | Gabriel Russell (Inactive) |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||
| Backwards Compatibility: | Fully Compatible | ||||||||||||
| Operating System: | ALL | ||||||||||||
| Sprint: | Dev Tools 2019-04-08 | ||||||||||||
| Participants: | |||||||||||||
| Description |
|
If the listDatabases command empty: false but does not specify a size for a collection, the shell will still show the collection as empty when running list databases. |
| Comments |
| Comment by Githook User [ 29/Mar/19 ] |
|
Author: {'name': 'Gabriel Russell', 'username': 'gabrielrussell', 'email': 'gabriel.russell@mongodb.com'}Message:
|
| Comment by David Golub [ 28/Mar/19 ] |
|
Looks good. Thanks so much for your work on this. |
| Comment by Bernie Hackett [ 12/Mar/19 ] |
|
My 2 cents: david.golub's request seems reasonable. The listDatabases command is returning "empty: false". The database is not empty. The shell prints "(empty)" after the database name because the sizeOnDisk field in the listDatabases response was rounded to 0, not because it actually is 0. This request isn't about the listDatabases command (or drivers or anything else), it's about the shell. Let me restate the request (correct me if I'm wrong David): When I type "list databases" in the mongo shell and hit enter, if the listDatabases command returns "empty: false" for a database, don't print "(empty)" after the database name. |