[SERVER-21768] Remove the 'numCollections' field from dbHash's response Created: 04/Dec/15 Updated: 17/May/19 Resolved: 08/Dec/15 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Internal Code |
| Affects Version/s: | None |
| Fix Version/s: | 3.2.1, 3.3.0 |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Kamran K. | Assignee: | Jonathan Abrahams |
| Resolution: | Done | Votes: | 0 |
| Labels: | test-only | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Backwards Compatibility: | Minor Change | ||||||||
| Backport Completed: | |||||||||
| Sprint: | TIG D (12/11/15) | ||||||||
| Participants: | |||||||||
| Linked BF Score: | 0 | ||||||||
| Description |
|
The 'numCollections' field in dbHash's response doesn't necessarily match the collection list that's returned because it a) doesn't factor in the filtering of system collections and b) it doesn't factor in the 'collections' filter list that the command can take. We should remove the numCollections field from the response (src/mongo/db/commands/dbhash.cpp) and update the JS tests that reference it (jstests/sharding/sync_cluster_config/sync2.js and jstests/concurrency/fsm_libs/cluster.js). |
| Comments |
| Comment by Githook User [ 11/Dec/15 ] |
|
Author: {u'username': u'hptabster', u'name': u'Jonathan Abrahams', u'email': u'jonathan@mongodb.com'}Message: (cherry picked from commit 9689f7e884c6c80f76c35f983e68a7fec8b27969) |
| Comment by Githook User [ 08/Dec/15 ] |
|
Author: {u'username': u'hptabster', u'name': u'Jonathan Abrahams', u'email': u'jonathan@mongodb.com'}Message: |
| Comment by Jonathan Abrahams [ 04/Dec/15 ] |
|
Alternately we could update the dbHash function to not include the system & filtered collections in the result of numCollections. |