DOCSP-1350 with php removed

Author: skerschb

Makefile

@@ -92,8 +92,10 @@ examples:
 	curl -SfL https://raw.githubusercontent.com/mongodb/mongo-java-driver/master/driver-legacy/src/examples/documentation/DocumentationSamples.java -o ${DRIVERS_PATH}/DocumentationSamples.java
 	curl -SfL https://raw.githubusercontent.com/mongodb/node-mongodb-native/2.2/test/functional/examples_tests.js -o ${DRIVERS_PATH}/examples_tests.js
 	curl -SfL https://raw.githubusercontent.com/mongodb/mongo-ruby-driver/master/spec/mongo/shell_examples_spec.rb -o ${DRIVERS_PATH}/shell_examples_spec.rb
+	curl -SfL https://raw.githubusercontent.com/mongodb/mongo-ruby-driver/master/spec/mongo/change_stream_examples_spec.rb -o ${DRIVERS_PATH}/change_stream_examples_spec.rb
 	curl -SfL https://raw.githubusercontent.com/mongodb/mongo-scala-driver/master/driver/src/it/scala/org/mongodb/scala/DocumentationExampleSpec.scala -o ${DRIVERS_PATH}/DocumentationExampleSpec.scala
 	curl -SfL https://raw.githubusercontent.com/mongodb/mongo-csharp-driver/master/tests/MongoDB.Driver.Examples/DocumentationExamples.cs -o ${DRIVERS_PATH}/DocumentationExamples.cs
 	curl -SfL https://raw.githubusercontent.com/mongodb/mongo-csharp-driver/master/tests/MongoDB.Driver.Examples/ChangeStreamExamples.cs -o ${DRIVERS_PATH}/ChangeStreamExamples.cs
 	curl -SfL https://raw.githubusercontent.com/mongodb/mongo-c-driver/master/tests/test-mongoc-sample-commands.c -o ${DRIVERS_PATH}/test-mongoc-sample-commands.c 
 	curl -Sfl https://raw.githubusercontent.com/mongodb/mongo-java-driver-reactivestreams/master/examples/documentation/src/DocumentationSamples.java -o ${DRIVERS_PATH}/AsyncDocumentationSamples.java
+	

source/tutorial/change-streams-example.txt

@@ -55,6 +55,13 @@ Change Stream Examples
          The examples below assume that you have `connected to a MongoDB replica set and have accessed a database
          <http://mongoc.org/libmongoc/current/tutorial.html#making-a-connection/>`__
          that contains an ``inventory`` collection.
+        
+     - id: ruby
+       content: |
+         The examples below assume that you have `connected to a MongoDB replica set and have accessed a database
+         <https://docs.mongodb.com/ruby-driver/master/tutorials/ruby-driver-create-client/>`_
+         that contains an ``inventory`` collection.
+
 
 Open A Change Stream
 --------------------
@@ -104,6 +111,16 @@ as long as a connection to the MongoDB deployment remains open *and* the collect
             :dedent: 0
             :start-after: Start Changestream Example 1
             :end-before: End Changestream Example 1
+            
+     - id: ruby
+       content: |
+         .. class:: copyable-code
+         
+         .. literalinclude:: /driver-examples/change_stream_examples_spec.rb
+            :language: ruby
+            :dedent: 4
+            :start-after: Start Changestream Example 1
+            :end-before: End Changestream Example 1
 
 In order to retrieve the data change event notifications, iterate
 the change stream ``cursor``.
@@ -147,7 +164,13 @@ Lookup Full Document for Update Operations
          To return the most current majority-committed version of the updated
          document, pass ``"FullDocument = ChangeStreamFullDocumentOption.UpdateLookup"`` to the
          :method:`collection.Watch()` method.
-
+         
+     - id: ruby
+       content: |
+         By default, change streams only return the delta of fields during the update operation. 
+         To return the most current majority-committed version of the updated
+         document, pass ``full_document: 'updateLookup'`` to the
+         :method:`watch()` method.
 
 If there are one or more majority-committed operations that modified the
 updated document *after* the update operation but *before* the lookup, the
@@ -206,6 +229,16 @@ update operation.
             :dedent: 0
             :start-after: Start Changestream Example 2
             :end-before: End Changestream Example 2
+            
+     - id: ruby
+       content: |
+         .. class:: copyable-code
+         
+         .. literalinclude:: /driver-examples/change_stream_examples_spec.rb
+            :language: php
+            :dedent: 4
+            :start-after: Start Changestream Example 2
+            :end-before: End Changestream Example 2
 
 See :ref:`change-stream-output` for more information on the change stream
 response document format.
@@ -268,16 +301,18 @@ response document format.
 Resume a Change Stream
 ----------------------
 
-Each change stream response document has an ``_id`` field that contains a
-document containing a resume token.  The ``resumeToken`` includes the change
-stream notification id. You can use the ``resumeToken`` document to resume
-notification after a specific notification.
+
 
 .. tabs-drivers::
 
    tabs:
      - id: python
        content: |
+         Each change stream response document has an ``_id`` field that contains a
+         document containing a resume token.  The ``resumeToken`` includes the change
+         stream notification id. You can use the ``resumeToken`` document to resume
+         notification after a specific notification.
+       
          In the example below, the ``resumeAfter`` modifier takes a parameter that must resolve to a resume
          token. Passing the ``resumeToken`` to the ``resumeAfter`` modifier directs
          the change stream to attempt to resume notifications starting at the
@@ -293,6 +328,11 @@ notification after a specific notification.
 
      - id: java-sync
        content: |
+         Each change stream response document has an ``_id`` field that contains a
+         document containing a resume token.  The ``resumeToken`` includes the change
+         stream notification id. You can use the ``resumeToken`` document to resume
+         notification after a specific notification.
+         
          In the example below, the ``resumeAfter()`` method takes a parameter that must resolve to a resume
          token. Passing the ``resumeToken`` to the ``resumeAfter()`` method directs
          the change stream to attempt to resume notifications starting at the
@@ -308,6 +348,11 @@ notification after a specific notification.
 
      - id: csharp
        content: |
+         Each change stream response document has an ``_id`` field that contains a
+         document containing a resume token.  The ``resumeToken`` includes the change
+         stream notification id. You can use the ``resumeToken`` document to resume
+         notification after a specific notification.
+         
          In the example below, the ``resumeToken`` is retrieved from the last change stream document
          and passed to the ``Watch()`` method as an option. Passing the ``resumeToken``
          to the ``Watch()`` method directs
@@ -324,6 +369,11 @@ notification after a specific notification.
 
      - id: c
        content: |
+         Each change stream response document has an ``_id`` field that contains a
+         document containing a resume token.  The ``resumeToken`` includes the change
+         stream notification id. You can use the ``resumeToken`` document to resume
+         notification after a specific notification.
+       
          In the example below, the ``resumeAfter`` option is appended to the stream options
          to recreate the stream after it has been destroyed. Passing the ``_id`` to
          the change stream attempts to resume notifications starting at the
@@ -336,6 +386,25 @@ notification after a specific notification.
             :dedent: 0
             :start-after: Start Changestream Example 3
             :end-before: End Changestream Example 3
+            
+     - id: ruby
+       content: |
+         Each change stream response document has an ``_id`` field which can be passed
+         to the ``watch()`` method, indicating to the method at what point in the
+         iteration of the change stream it should resume.
+         
+         In the example below, the ``resumeAfter`` option is passed to the ``watch()`` method
+         with a value of the ``_id`` of the last document processed, in order to recreate the
+         stream after it has been destroyed. Passing the ``_id`` to the change stream attempts 
+         to resume notifications starting at the operation specified.
+         
+         .. class:: copyable-code
+         
+         .. literalinclude:: /driver-examples/change_stream_examples_spec.rb
+            :language: ruby
+            :dedent: 4
+            :start-after: Start Changestream Example 3
+            :end-before: End Changestream Example 3
 
 
 As long as that operation has not rolled off the :term:`oplog`, the