[DOCS-6736] Comment on: "manual/core/write-operations-atomicity.txt" Created: 07/Dec/15  Updated: 08/Dec/16  Resolved: 14/Dec/15

Status: Closed
Project: Documentation
Component/s: None
Affects Version/s: None
Fix Version/s: None

Type: Improvement Priority: Trivial - P5
Reporter: Docs Collector User (Inactive) Assignee: Kyle Suarez
Resolution: Done Votes: 1
Labels: collector-298ba4e7
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

Any

Location: https://docs.mongodb.org/manual/core/write-operations-atomicity/
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:31.0) Gecko/20100101 Firefox/31.0
Screen Resolution: 1920 x 1200
repo: docs
source: core/write-operations-atomicity


Participants:
Days since reply: 7 years, 29 weeks ago

 Description   

Two problems.

First, the following sentence is clearly broken:

An approach may be to create a unique index on a field (or fields) that should have only unique values (or unique combination of values) prevents duplicate insertions or updates that result in duplicate values.

Second, the entire "document-level atomicity" discussion does not make clear whether said atomicity is at the level of the leaves (the documents embedded within documents) or the roots (the outer, enclosing documents that are direct members of the collection).



 Comments   
Comment by Emily Hall [ 27/Jul/16 ]

Closed for housekeeping on 7/27/2016 by Emily Hall.
If you require additional support, please open a new ticket for prioritization.
Thanks,
Emily

Comment by Kyle Suarez [ 14/Dec/15 ]

Resolved in https://github.com/mongodb/docs/commit/71306afc493d546fb185409a8f37b69282dd78b8

Comment by Githook User [ 14/Dec/15 ]

Author:

{u'username': u'ksuarz', u'name': u'Kyle Suarez', u'email': u'kyle.suarez@mongodb.com'}

Message: DOCS-6736 reword atomicity and unique indexes

Signed-off-by: kay <kay.kim@10gen.com>
Branch: master
https://github.com/mongodb/docs/commit/71306afc493d546fb185409a8f37b69282dd78b8

Comment by Githook User [ 14/Dec/15 ]

This ticket number is incorrect; the commit below is for DOCS-6738

Author:

Unknown macro: {u'username'}

Message: DOCS-6736 fix unit spacing

Ensures that a space is placed between a number and a unit; for example,
"64 GB".

In the GridFS documentation, "k" has been converted to "KB" when discussing
chunk size.

A hyphen is used for "32-bit" and "64-bit."

Signed-off-by: kay <kay.kim@10gen.com>
Branch: master
https://github.com/mongodb/docs/commit/5edb84f5c2655a2d721af1de0433bf1a42ed95d9

Comment by Kyle Suarez [ 11/Dec/15 ]

DUThibault, thanks for the ticket. I'm reworking the section on using unique indexes to read more clearly.

As for your "document-level atomicity" question, I believe the documentation addresses that here:

In MongoDB, a write operation is atomic on the level of a single document, even if the operation modifies multiple embedded documents within a single document.

Generated at Thu Feb 08 07:52:53 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.