Uploaded image for project: 'Core Server'
  1. Core Server
  2. SERVER-10214

New update logic does not honor 'timestamp(0)' fixups during object replacement.

    XMLWordPrintableJSON

Details

    • Icon: Task Task
    • Resolution: Done
    • Icon: Major - P3 Major - P3
    • 2.5.2
    • None
    • Write Ops
    • None

    Description

      When updating an object with an object replacement (rather than a $mod), if the new object value contains a Timestamp(0) field in the first or second position, then the field is not reset to OpTime now as it should be.

      This was the cause of the client tests failing when run with the new update codepath enabled.

      Attachments

        Activity

          People

            andrew.morrow@mongodb.com Andrew Morrow (Inactive)
            andrew.morrow@mongodb.com Andrew Morrow (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: