DOCSP-17524-TOOLS docs repo adds matching warning

Author: mungitoperrito

source/includes/warning-tools-dot-dollar-import-export-restriction.rst

@@ -0,0 +1,20 @@
+.. warning:: Data Import and Export Conflicts With (``$``) and (``.``)
+
+   Starting in MongoDB 5.0, document field names can be (``$``)
+   prefixed and can contain a (``.``). However,
+   :binary:`~bin.mongoimport` and :binary:`~bin.mongoexport` should not
+   be used with field names that make use of these characters.
+
+   :ref:`MongoDB Extended JSON v2 <extended-json-high-level-ref-v2>`
+   cannot differentiate between type wrappers and fields that happen to
+   have the same name as type wrappers. Do not use Extended JSON
+   formats in contexts where the corresponding BSON representations
+   might include (``$``) prefixed keys. The
+   :ref:`DBRef <dbref-explanation>` mechanism is an exception to this
+   general rule. 
+
+   There are also restrictions on using :binary:`~bin.mongoimport` and
+   :binary:`~bin.mongoexport` with (``.``) in field names. Since CSV
+   files use the (``.``) to represent data hierarchies, a (``.``) in a
+   field name will be misinterpreted as a level of nesting.
+

source/mongoexport.txt

@@ -302,6 +302,8 @@ If you specify read preference in the URI string and the
 :option:`--readPreference <mongoexport --readPreference>` value
 overrides the read preference specified in the URI string.
 
+.. include:: /includes/warning-tools-dot-dollar-import-export-restriction.rst
+
 .. _mongoexport-options:
 
 Options

source/mongoimport.txt

@@ -144,6 +144,8 @@ with the :option:`--auth <mongod.--auth>` option, you must use the
 possess, at a minimum, the :authrole:`readWrite` role on the database
 into which they are importing data.
 
+.. include:: /includes/warning-tools-dot-dollar-import-export-restriction.rst
+
 Options
 -------