[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:
Related
Participants:
Days since reply: 9 years, 33 weeks, 2 days ago

 Description   

The entry in the mongodump documentation under --forceTableScan mentions:

typically, mongodump saves entries as they appear in the index of the _id field

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: DOCS-3667: fixing note about index selection on forceTableScan on mongodump
Branch: master
https://github.com/mongodb/docs/commit/1c5718bc46cc6041a978673aa3488900fad62894

Generated at Thu Feb 08 07:46:14 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.