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

XMLWordPrintableJSON

    • Type: Task
    • Resolution: Done
    • Priority: Major - P3
    • 2.5.2
    • Affects Version/s: None
    • Component/s: Write Ops
    • None
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      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.

            Assignee:
            Andrew Morrow (Inactive)
            Reporter:
            Andrew Morrow (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: