nModified should be null from legacy writes

XMLWordPrintableJSON

    • Type: Task
    • Resolution: Done
    • Priority: Major - P3
    • None
    • Component/s: None
    • None

      Related to DRIVERS-143, obviously. DRIVERS-143 is about the Bulk API's merged results from a series of operations.

      This ticket is about the simple "update" operation. If a driver uses the new "update" command, the 2.6 server responds with an accurate count of documents actually changed, in the "nModified" field. For example, if a document has "x: 1" and you use the "update" command to set x to 1, the server responds with "nModified: 0".

      This behavior is impossible to simulate with OP_UPDATE, so drivers shouldn't return an nModified field as the result of a legacy update operation. Depending on the language, the field should be absent, or NULL, or attempting to access it should raise an exception.

            Assignee:
            Barrie Segal (Inactive)
            Reporter:
            Barrie Segal (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

              Created:
              Updated:
              Resolved: