[DOCS-9983] In the 3.0 and later manuals it says "... must use mongoimport while connected to a mongod instance." Created: 08/Mar/17 Updated: 30/Oct/23 Resolved: 30/Oct/17 |
|
| Status: | Closed |
| Project: | Documentation |
| Component/s: | tools |
| Affects Version/s: | None |
| Fix Version/s: | Server_Docs_20231030 |
| Type: | Improvement | Priority: | Major - P3 |
| Reporter: | William Byrne III | Assignee: | Kay Kim (Inactive) |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Environment: |
Documentation for versions 3.0, 3.2, and 3.4 re mongoimport, mongoexport, mongodump, mongorestore |
||
| Participants: | |
| Days since reply: | 6 years, 49 weeks ago |
| Description |
|
When mongoimport, mongoexport, mongodump and mongrestore were rebuilt in Go in version 3.0, they could no longer link in in libraries from mongod and thus could not read/write from/to the files in the DBPATH without going via a running mongod. For all four tools there is a comment/warning like: "Changed in version 3.0.0: mongoimport removed the --dbpath as well as related
This confused my customer with a sharded cluster who tried to bypass his mongos to write directly to a mongod for the shard ... The comment/warning should be updated to something like " ... without going via a running mongod or mongos as appropriate." |
| Comments |
| Comment by Githook User [ 08/Mar/17 ] |
|
Author: {u'username': u'kay-kim', u'name': u'kay', u'email': u'kay.kim@10gen.com'}Message: |
| Comment by Githook User [ 08/Mar/17 ] |
|
Author: {u'username': u'kay-kim', u'name': u'kay', u'email': u'kay.kim@10gen.com'}Message: |
| Comment by Githook User [ 08/Mar/17 ] |
|
Author: {u'username': u'kay-kim', u'name': u'kay', u'email': u'kay.kim@10gen.com'}Message: |