[DOCS-3667] mongodump --forceTableScan behavior Created: 27/Jun/14 Updated: 16/Mar/15 Resolved: 30/Jun/14 |
|
| Status: | Closed |
| Project: | Documentation |
| Component/s: | manual |
| Affects Version/s: | mongodb-2.6 |
| Fix Version/s: | v1.3.7 |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Andre de Frere | Assignee: | Sam Kleinman (Inactive) |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||
| Participants: | |||||
| Days since reply: | 9 years, 33 weeks, 2 days ago | ||||
| Description |
|
The entry in the mongodump documentation under --forceTableScan mentions:
This is only true when no query is given to mongodump. If a query is given, then the index used would be whatever the query optimiser chooses. |
| Comments |
| Comment by Githook User [ 30/Jun/14 ] |
|
Author: {u'username': u'tychoish', u'name': u'Sam Kleinman', u'email': u'samk@10gen.com'}Message: |