[SERVER-12837] upgradeCheck() prints way too much output in default mode Created: 21/Feb/14 Updated: 21/Jan/16 Resolved: 21/Jan/16 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Admin |
| Affects Version/s: | 2.6.0-rc0 |
| Fix Version/s: | None |
| Type: | Improvement | Priority: | Major - P3 |
| Reporter: | Asya Kamsky | Assignee: | Unassigned |
| Resolution: | Won't Fix | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Participants: | |||||||||
| Description |
|
Running upgradeCheck() it turned out I had a large collection where all documents were "non-compliant" - having all of them echo'ed to stdout seems useless - how about verbose mode that does that and normal mode that just counts how many documents are out of compliance and outputs for each DB/collection the count? |
| Comments |
| Comment by Daniel Pasette (Inactive) [ 23/Feb/14 ] |
|
the intent is to print them out (or redirect output to a file) so you can deal with them before upgrade. |