Skip to content

Commit d6b8096

Browse files
author
matulef
committed
Update source/release-notes/2.4.txt
1 parent 8b4c21d commit d6b8096

File tree

1 file changed

+8
-8
lines changed

1 file changed

+8
-8
lines changed

source/release-notes/2.4.txt

Lines changed: 8 additions & 8 deletions
Original file line numberDiff line numberDiff line change
@@ -354,30 +354,30 @@ the :program:`mongo` shell that resembles the following:
354354

355355
This operation shards the ``active`` collection in the ``records``
356356
database, using a hash of the ``a`` field as the shard
357-
key. Consider the following properties when a hashed shard key:
357+
key. Consider the following properties when using a hashed shard key:
358358

359359
- As with other kinds of shard key indexes, if your collection has
360-
data, you must create the hashed index before sharding. If you
360+
data, you must create the hashed index before sharding. If your
361361
collection does not have data, sharding the collection will create
362362
the appropriate index.
363363

364-
- The :program:`mongos` can route all equality queries to a specific
365-
shards or set of shards using the hashed index; however, the
366-
:program:`mongos` must route range queries to all shards.
364+
- The :program:`mongos` will route all equality queries to a specific
365+
shard or set of shards; however, the :program:`mongos` must route
366+
range queries to all shards.
367367

368368
- When using a hashed shard key on a collection without data, MongoDB
369369
automatically pre-splits the range of 64-bit hash values into
370370
chunks. By default, the initial number of chunks is equal to twice
371371
the number of shards at creation time. You can change the number of
372372
chunks created, using the ``numInitialChunks`` option, as in the
373-
following invocation of ``numInitialChunks``:
373+
following invocation of ``shardCollection``:
374374

375375
.. code-block:: javascript
376376

377-
db.adminCommand( { shardCollection: "test.collection", key: { a: "hashed"}, numInitialChunks: 9001 } )
377+
db.adminCommand( { shardCollection: "test.collection", key: { a: "hashed"}, numInitialChunks: 2001 } )
378378

379379
.. warning::
380380

381-
Avoid using hashed shard keys when the hashed field has floating
381+
Avoid using hashed shard keys when the hashed field has non-integral floating
382382
point values, see :ref:`hashed indexes <hashed-index-warning>` for
383383
more information.

0 commit comments

Comments
 (0)