@@ -10,11 +10,11 @@ operation; however, some cases require additional import and export
10
10
functionality.
11
11
12
12
This document provides an overview of the import and export tools
13
- provided in distributions of MongoDB administrators. These utilities
13
+ provided in distributions for MongoDB administrators. These utilities
14
14
are useful when you want to backup or export a portion of your
15
15
database without capturing the state of the entire database. For more
16
16
complex data migration tasks, you may want to write your own import
17
- and export scripts using a client driver :term: `driver ` to interact
17
+ and export scripts using a client :term: `driver ` to interact
18
18
with the database itself.
19
19
20
20
.. warning ::
@@ -23,9 +23,16 @@ with the database itself.
23
23
:program: `mongod ` instance, they can impact the performance of your
24
24
running database.
25
25
26
+ TODO Do you want to mention why? For instance, traversing your entire
27
+ database will pull in ALL data, potentially evicting current working
28
+ set. This could be potentially linked to some page discussing
29
+ memory mapped files, etc...
30
+
26
31
:program: `mongoimport ` and :program: `mongoexport ` do not reliably
27
32
preserve data types. As a result data exported or imported with
28
- these tools may loose some measure of fidelity. Use with care.
33
+ these tools may lose some measure of fidelity. Use with care.
34
+
35
+ TODO link to caveat section about which types are kept or lost
29
36
30
37
Using Database Imports and Exports for Backups
31
38
----------------------------------------------
@@ -37,10 +44,10 @@ tools and operations discussed provide functionality that's useful in
37
44
the context of providing some kinds of backups.
38
45
39
46
By contrast, use import and export tools to backup a small subset of
40
- your data. These backups may capture a small crucial set of data or a
41
- frequently modified section of data, for extra insurance, or for ease
42
- of access. No matter how you decide to import or export your data,
43
- consider the following guidelines:
47
+ your data or to move data to or from a 3rd party system. These backups may
48
+ capture a small crucial set of data or a frequently modified section of
49
+ data, for extra insurance, or for ease of access. No matter how you
50
+ decide to import or export your data, consider the following guidelines:
44
51
45
52
- Label files so that you can identify what point in time the
46
53
export or backup reflects.
@@ -51,7 +58,7 @@ consider the following guidelines:
51
58
- Do not create or apply exports if the backup process itself will
52
59
have an adverse effect on a production system.
53
60
54
- - Make sure that the reflect a consistent data state. Export or backup
61
+ - Make sure that they reflect a consistent data state. Export or backup
55
62
processes can impact data integrity (i.e. type fidelity) and
56
63
consistency if updates continue during the backup process.
57
64
@@ -61,8 +68,8 @@ consider the following guidelines:
61
68
Human Intelligible Import/Export Formats
62
69
----------------------------------------
63
70
64
- This section describes a process for your database, or a portion
65
- thereof, to a file in a JSON or CSV format.
71
+ This section describes a process to import/export your database,
72
+ or a portion thereof, to a file in a JSON or CSV format.
66
73
67
74
.. seealso :: The :doc:`/reference/mongoimport` and
68
75
:doc: `/reference/mongoexport ` documents contain complete
@@ -76,7 +83,7 @@ thereof, to a file in a JSON or CSV format.
76
83
may be more suited to this task. The :program: `mongo ` shell
77
84
provides the :func: `db.copyDatabase() ` method.
78
85
79
- These tools may also be useful for importing data into a MongoDB data
86
+ These tools may also be useful for importing data into a MongoDB database
80
87
from third party applications.
81
88
82
89
Database Export with mongoexport
@@ -174,9 +181,9 @@ MongoDB instance's database files. Consider using the
174
181
files when you run :program: `mongoimport ` in this configuration.
175
182
176
183
Use the ":option: `--ignoreBlanks <mongoimport --ignoreBlanks> `" option
177
- to ensure that blank fields are. For CSV and TSV imports, this option
178
- provides the desired functionality in most cases: it avoids inserting
179
- blank fields in MongoDB documents.
184
+ to ensure that blank fields are ignored . For CSV and TSV imports, this
185
+ option provides the desired functionality in most cases: it avoids
186
+ inserting blank fields in MongoDB documents.
180
187
181
188
.. seealso :: See the ":doc:`/administration/backups`" document for
182
189
more in depth information about backing up MongoDB
0 commit comments