Skip to content

Missing full stop and "to" #883

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
wants to merge 1 commit into from
Closed

Missing full stop and "to" #883

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
6 changes: 3 additions & 3 deletions source/tutorial/shard-gridfs-data.txt
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -14,7 +14,7 @@ collection. The ``files`` collection is typically small, and only
contains metadata. None of the required keys for GridFS lend
themselves to an even distribution in a sharded situation. If you
*must* shard the ``files`` collection, use the ``_id`` field
possibly in combination with an application field
possibly in combination with an application field.

Leaving ``files`` unsharded means that all the file metadata
documents live on one shard. For production GridFS stores you *must*
Expand All @@ -32,8 +32,8 @@ issue commands similar to the following:

db.runCommand( { shardCollection : "test.fs.chunks" , key : { files_id : 1 , n : 1 } } )

You may also want shard using just the ``file_id`` field, as in the
following operation:
You may also want to shard using just the ``file_id`` field, as in
the following operation:

.. code-block:: javascript

Expand Down