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

Rewrite some sharding tests to avoid using chunk versions with Timestamp(0, 0)

XMLWordPrintableJSON

    • Type: Icon: Task Task
    • Resolution: Fixed
    • Priority: Icon: Major - P3 Major - P3
    • 5.2.0, 5.1.0-rc2
    • Affects Version/s: None
    • Component/s: Sharding
    • None
    • Fully Compatible
    • v5.1
    • Sharding EMEA 2021-10-04, Sharding EMEA 2021-10-18
    • 46

      Timestamp(0, 0) has a special meaning (i.e. get the current time) as we saw in BF-22784.

      Since we are not actually creating collections with this timestamp the goal of this ticket is to revisit the tests changed in SERVER-52847, changing the default constructed timestamps by a valid one.

            Assignee:
            allison.easton@mongodb.com Allison Easton
            Reporter:
            sergi.mateo-bellido@mongodb.com Sergi Mateo Bellido
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated:
              Resolved: