Skip to content

Commit 2aeddb2

Browse files
author
Bob Grabar
committed
DOCS-390 ongoing edits #4 RN 2.0 migration
1 parent 00fddf6 commit 2aeddb2

File tree

2 files changed

+33
-27
lines changed

2 files changed

+33
-27
lines changed
Lines changed: 9 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,9 @@
1+
:orphan:
2+
3+
======================
4+
Changes in MongoDB 2.0
5+
======================
6+
7+
.. toctree::
8+
9+
2.0

draft/release-notes/2.0.txt

Lines changed: 24 additions & 27 deletions
Original file line numberDiff line numberDiff line change
@@ -24,17 +24,16 @@ There are a few changes you must be aware of before attempting to
2424
upgrade. Read through all release notes before upgrading, and ensure
2525
that no changes will affect your deployment.
2626

27-
If you create new indexes in 2.0, then downgrading to 1.8 :wiki:`is
28-
possible <mongo+-+Index+Versions>` but reindexing the new collections
29-
will be required.
27+
If you create new indexes in 2.0, then downgrading to 1.8
28+
:wiki:`is possible <mongo+-+Index+Versions>`
29+
but reindexing the new collections will be required.
3030

3131
``mongoimport`` and ``mongoexport`` now correctly adhere to the CSV spec
3232
for handling CSV input/output. This may break existing import/export
3333
workflows if they relied on the broken behavior. For more information
34-
see the related `JIRA case
35-
<https://jira.mongodb.org/browse/SERVER-1097>`.
34+
see the related `JIRA case <https://jira.mongodb.org/browse/SERVER-1097>`_.
3635

37-
`Journaling <http://api.mongodb.org/wiki/current/Journaling.html>` is
36+
`Journaling <http://api.mongodb.org/wiki/current/Journaling.html>`_ is
3837
**enabled by default** in 2.0 for 64-bit builds. If you still prefer to
3938
run without journaling, start :program:`mongod` with the ``--nojournal``
4039
option. Otherwise, the journal files will be created on startup. The
@@ -69,10 +68,10 @@ Upgrading a Replica Set
6968
#. To avoid losing the last few updates on failover you can
7069
temporarily halt your application (failover should take less than 10
7170
seconds) or change your application code to
72-
`confirm that each update reaches multiple servers <http://api.mongodb.org/wiki/current/Verifying%20Propagation%20of%20Writes%20with%20getLastError.html>`.
71+
`confirm that each update reaches multiple servers <http://api.mongodb.org/wiki/current/Verifying%20Propagation%20of%20Writes%20with%20getLastError.html>`_.
7372

7473
#. Use the :method:`rs.stepDown()` to step down the primary to allow
75-
the normal :ref:`failover <replica-set-failover>` procedure.
74+
the normal :ref:`failover <mongo+-+replica-set-failover>` procedure.
7675

7776
:method:`rs.stepDown()` and :dbcommand:`replSetStepDown` provide for
7877
shorter and more consistent failover procedures than simply
@@ -109,7 +108,7 @@ Concurrency Improvements
109108
When going to disk, the server will yield the write lock if the data
110109
being acted upon isn't likely to be in memory. The initial
111110
implementation of this feature now exists:
112-
`(SERVER-2563) <https://jira.mongodb.org/browse/SERVER-2563>`
111+
`(SERVER-2563) <https://jira.mongodb.org/browse/SERVER-2563>`_
113112

114113
The specific operations yield in 2.0 are:
115114

@@ -132,7 +131,7 @@ system setting or 1MB.
132131
Index Performance Enhancements
133132
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
134133

135-
v2.0 includes `significant improvements to the index structures <http://api.mongodb.org/wiki/current/Index%20Versions.html>`.
134+
v2.0 includes `significant improvements to the index structures <http://api.mongodb.org/wiki/current/Index%20Versions.html>`_.
136135
Indexes are often 25% smaller and 25% faster (depends on the use case).
137136
When upgrading from previous versions, the benefits of the new index
138137
type are realized only if you create a new index or re-index an old one.
@@ -195,12 +194,12 @@ which would succeed if it fulfilled the conditions the DBA defined for
195194
"very important write".
196195

197196
For more information, see the
198-
`tagging documentation <http://api.mongodb.org/wiki/current/Data%20Center%20Awareness.html#DataCenterAwareness-Tagging%28version2.0%29>`.
197+
`tagging documentation <http://api.mongodb.org/wiki/current/Data%20Center%20Awareness.html#DataCenterAwareness-Tagging%28version2.0%29>`_.
199198

200199
Your driver may also support tag-aware reads. Instead of simply
201200
specifying ``slaveOk``, you specify ``slaveOk`` with tags indicating which
202201
data-centers you want to read from. See your
203-
`driver <http://docs.mongodb.org/manual/applications/drivers/>`
202+
`driver <http://docs.mongodb.org/manual/applications/drivers/>`_
204203
for details.
205204

206205
``w`` : ``majority``
@@ -219,8 +218,7 @@ Reconfiguration with a minority up
219218
If the majority of servers in a set has been permanently lost, you can
220219
now force a reconfiguration of the set to bring it back online.
221220

222-
See more information on :ref:`Reconfiguring a replica set when members are
223-
down <http://www.mongodb.org/display/DOCS/Reconfiguring+a+replica+set+when+members+are+down>``.
221+
See more information on :ref:`Reconfiguring a replica set when members are down <mongo+-+http://www.mongodb.org/display/DOCS/Reconfiguring+a+replica+set+when+members+are+down>`.
224222

225223
Primary checks for a caught up secondary before stepping down
226224
`````````````````````````````````````````````````````````````
@@ -231,7 +229,7 @@ within 10 seconds of its latest optime. You can force the primary to
231229
step down anyway, but by default it will return an error message.
232230

233231
See also
234-
:ref:`Forcing a Member to be Primary <http://www.mongodb.org/display/DOCS/Forcing+a+Member+to+be+Primary>`.
232+
:ref:`Forcing a Member to be Primary <mongo+-+http://www.mongodb.org/display/DOCS/Forcing+a+Member+to+be+Primary>`.
235233

236234
Extended shutdown on the primary to minimize interruption
237235
`````````````````````````````````````````````````````````
@@ -268,7 +266,7 @@ objects, embedded either inline or in nested sub-documents. Additional
268266
command options are also supported, allowing results to be returned with
269267
not only distance but the location used to generate the distance.
270268

271-
For more information, see the :ref:`Geospatial documentation <http://www.mongodb.org/display/DOCS/Geospatial+Indexing#GeospatialIndexing-MultilocationDocuments>`.
269+
For more information, see the :ref:`Geospatial documentation <mongo+-+http://www.mongodb.org/display/DOCS/Geospatial+Indexing#GeospatialIndexing-MultilocationDocuments>`.
272270

273271
Polygon searches
274272
````````````````
@@ -297,14 +295,14 @@ New ``ContinueOnError`` option for bulk insert
297295
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
298296

299297
When this flag is set (see your
300-
`driver <http://docs.mongodb.org/manual/applications/drivers/>`
298+
`driver <http://docs.mongodb.org/manual/applications/drivers/>`_
301299
on how to set it), bulk insert will continue to insert any remaining
302300
documents even if an insert fails (due, for example, to a duplicate
303301
key). The :dbcommand:`getLastError` command will report whether any
304302
doc inserts have failed (not just last one). If multiple errors occur,
305303
only the most recent will be reported by :dbcommand:`getLastError`.
306304

307-
See :ref:`OP_INSERT <http://www.mongodb.org/display/DOCS/Mongo+Wire+Protocol#MongoWireProtocol-OPINSERT>`.
305+
See :ref:`OP_INSERT <mongo+-+http://www.mongodb.org/display/DOCS/Mongo+Wire+Protocol#MongoWireProtocol-OPINSERT>`.
308306

309307
Map Reduce
310308
~~~~~~~~~~
@@ -318,7 +316,7 @@ map/reduce to a sharded collection. Combined with the ``reduce`` or
318316
collections from map/reduce jobs.
319317

320318
For more information, see the
321-
:ref:`output options <http://www.mongodb.org/display/DOCS/MapReduce#MapReduce-Outputoptions>`.
319+
:ref:`output options <mongo+-+http://www.mongodb.org/display/DOCS/MapReduce#MapReduce-Outputoptions>`.
322320
documentation.
323321

324322
Performance improvements
@@ -342,7 +340,7 @@ Additional regex options: ``s``
342340

343341
Allows the dot (.) to match all characters including new lines. This is
344342
in addition to the currently supported ``i``, ``m`` and ``x``. See
345-
:ref:`Using regular expressions in queries <http://www.mongodb.org/display/DOCS/Advanced+Queries#AdvancedQueries-RegularExpressions>`.
343+
:ref:`Using regular expressions in queries <mongo+-+http://www.mongodb.org/display/DOCS/Advanced+Queries#AdvancedQueries-RegularExpressions>`.
346344

347345
$and
348346
````
@@ -367,7 +365,7 @@ You can define a custom prompt for the :program:`mongo` shell. You can
367365
change the prompt at any time by setting the prompt variable to a string
368366
or a custom JavaScript function returning a string. For examples, see the
369367
documentation on
370-
:ref:`Custom Prompt <http://www.mongodb.org/display/DOCS/Overview+-+The+MongoDB+Interactive+Shell#Overview-TheMongoDBInteractiveShell-CustomPrompt>`.
368+
:ref:`Custom Prompt <mongo+-+http://www.mongodb.org/display/DOCS/Overview+-+The+MongoDB+Interactive+Shell#Overview-TheMongoDBInteractiveShell-CustomPrompt>`.
371369

372370
Default shell init script
373371
`````````````````````````
@@ -381,10 +379,9 @@ automatically, start the shell with ``--norc``.
381379

382380
For more information, see :doc:`mongo`.
383381

384-
See Also
385-
386-
- `MongoDB Download Page`_
387-
388-
- :ref:`Full list of changes on JIRA <https://jira.mongodb.org/secure/IssueNavigator.jspa?mode=hide&requestId=11002>`
382+
Resources
383+
---------
389384

390-
- :ref:`All backward incompatible changes <https://jira.mongodb.org/secure/IssueNavigator.jspa?requestId=11023>`
385+
- `MongoDB Downloads <http://mongodb.org/downloads>`_
386+
- `All JIRA Issues resolved in 2.0 <https://jira.mongodb.org/secure/IssueNavigator.jspa?mode=hide&requestId=11002>`_
387+
- `All Backward Incompatible Changes <https://jira.mongodb.org/secure/IssueNavigator.jspa?requestId=11023>_`

0 commit comments

Comments
 (0)