[SERVER-3023] The 'validate' output document returned from a mongos should have a 'valid' field at the top level. Created: 29/Apr/11 Updated: 12/Jul/16 Resolved: 09/May/11 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Sharding |
| Affects Version/s: | None |
| Fix Version/s: | 1.9.1 |
| Type: | Improvement | Priority: | Major - P3 |
| Reporter: | Bernie Hackett | Assignee: | Mathias Stearn |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Environment: |
ALL |
||
| Participants: |
| Description |
|
When running 'validate' against a collection in a sharded system the top level of the output document should have a 'valid' field. Currently drivers have to iterate through the subdocuments of 'raw' checking if each individual shard is valid. This becomes even more complicated when one shard has 1.8 members and another has 1.9 members since the <= 1.8 members don't return a 'valid' field at all. |
| Comments |
| Comment by auto [ 09/May/11 ] |
|
Author: {u'login': u'RedBeard0531', u'name': u'Mathias Stearn', u'email': u'mathias@10gen.com'}Message: Mongos validate command collects top-level "valid" field |