Skip to content

Commit a4ffbb0

Browse files
authored
DOCSP-38105 fixing build errors (#137)
* DOCSP-38105 fixing build errors * DOCSP-38105 fixing build errors
1 parent 2c6e783 commit a4ffbb0

File tree

2 files changed

+1
-15
lines changed

2 files changed

+1
-15
lines changed

source/mongodump/mongodump-behavior.txt

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -136,7 +136,7 @@ collection metadata which includes the following properties:
136136

137137
If :binary:`~bin.mongodump` outputs to standard output (``stdout``), the
138138
output does not include metadata. For more information, see the
139-
:option:`--out` option.
139+
:option:`--out <mongodump --out>` option.
140140

141141
Metadata Format
142142
~~~~~~~~~~~~~~~

source/mongorestore.txt

Lines changed: 0 additions & 14 deletions
Original file line numberDiff line numberDiff line change
@@ -173,20 +173,6 @@ Rebuild Indexes
173173
``mongorestore`` recreates indexes recorded by
174174
:binary:`~bin.mongodump` after restoring data.
175175

176-
.. note::
177-
178-
For MongoDB installations with ``featureCompatibilityVersion`` (fCV)
179-
set to ``"4.0"`` or earlier, creating indexes will
180-
:limit:`error if an index key in an existing document exceeds the
181-
limit <Index Key Limit>`.
182-
183-
To avoid this issue, consider using hashed indexes or indexing a
184-
computed value instead. If you want to resolve the index issue after
185-
restoring the data, you can disable the default index key length
186-
validation on the target database by setting the :binary:`~bin.mongod`
187-
instance's :parameter:`failIndexKeyTooLong` parameter to false.
188-
189-
190176
Exclude ``system.profile`` Collection
191177
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
192178

0 commit comments

Comments
 (0)