[DOCS-1387] shardCollection command's unique option is not documented Created: 12/Apr/13 Updated: 30/Oct/23 Resolved: 12/Apr/13 |
|
| Status: | Closed |
| Project: | Documentation |
| Component/s: | manual |
| Affects Version/s: | None |
| Fix Version/s: | Server_Docs_20231030 |
| Type: | Improvement | Priority: | Minor - P4 |
| Reporter: | Jeremy Mikola | Assignee: | Ed Costello |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Participants: | |
| Days since reply: | 10 years, 44 weeks, 2 days ago |
| Description |
|
Comparing:
The command documentation does not mention the unique option. If you inspect the source of sh.shardCollection in the JS shell, you'll see that it's unique argument simply sets the unique field on the command BSON object to true. |
| Comments |
| Comment by auto [ 15/Apr/13 ] |
|
Author: {u'date': u'2013-04-12T16:32:51Z', u'name': u'Ed Costello', u'email': u'epc@10gen.com'}Message: Signed-off-by: Sam Kleinman <samk@10gen.com> |
| Comment by Ed Costello [ 12/Apr/13 ] |
|
Fixed in github.com/epc/docs/ |