DOCS-133 document applyOps #86
Conversation
|
Updated with suggested revisions. |
|
yeah, the writelock/see lines are both comments that shouldn't be visable at all. so that's fine. |
|
|
||
| :dbcommand:`applyOps` is an internal command that supports sharding | ||
| functionality. | ||
| functionality. It applies a command object entry from an :term:`oplog` against a :term:`collection`. |
There was a problem hiding this comment.
sorry, I didn't catch this earlier, but I think we can just say "It applies entries from an oplog," I'm not sure "a command object entry," makes sense.
If we want to be really extravagant, we could also say, "It applies oplog entries passed to the command in the <operations> array, to a database, or collection if you specify the ns option."
Correspondingly, we should probably change the "array of operations to perform," to "array of operations to apply."
There was a problem hiding this comment.
That was my initial understanding, but on re-reading the code there's
actually no mention of an oplog at all. It takes oplog entries but applies
them against a collection, used to replay the oplog on shards or replica
sets.
ApplyOps itself is a wrapper around applyOperation_inlock.
On Tue, Jul 24, 2012 at 11:03 PM, Sam Kleinman <
[email protected]
wrote:
:dbcommand:`applyOps` is an internal command that supports sharding
- functionality.
- functionality. It applies a command object entry from an
:term:oplogagainst a :term:collection.sorry, I didn't catch this earlier, but I think we can just say "It
applies entries from an oplog," I'm not sure "a command object entry,"
makes sense.If we want to be really extravagant, we could also say, "It applies oplog
entries passed to the command in the<operations>array, to a
database, or collection if you specify thensoption."Correspondingly, we should probably change the "array of operations to
perform," to "array of operations to apply."
Reply to this email directly or view it on GitHub:
https://github.com/mongodb/docs/pull/86/files#r1232017
-ed costello
@epc https://twitter.com/epc / +19179752073
There was a problem hiding this comment.
I think this is consistent with the change that I suggested, but I could be wrong.
|
Added suggested changes. |
* DCOSP-29004 outdate version info * Review feedback
DOCSP-35643 Correct Latest Release Version
* (DOCSP-26581) Adds release notes and updates version * Sets submodule to v1.3.0
* fix line blocks and changelog link
DOCSP-27072: Added tombstone.on.delete setting.
[JIRA](https://jira.mongodb.org/browse/DOCSP-35773) [STAGING](https://preview-mongodbsarahsimpers.gatsbyjs.io/ops-manager/DOCSP-35773/release-notes/application/) [BUILD](https://workerpool-boxgs.mongodbstitch.com/pages/job.html?collName=queue&jobId=65c61e6a6b2f17c95a7e7da9) Confirmed dates based on the MongoDB Agent page and the dates of creation for these tickets: - https://jira.mongodb.org/browse/DOCSP-35343 - https://jira.mongodb.org/browse/DOCSP-36184
flesh out documentation for applyOps