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

Resharding always write new collection timestamp

    XMLWordPrintable

Details

    • Fully Compatible
    • v5.0
    • Sharding EMEA 2021-08-09

    Description

      In SERVER-58589 we removed the ShardingFullDDLSupportTimestampedVersion flag so that we always use timestamps in collection metadata.

      We forgot to cleanup some resharding code that still support the old metadata format. In particular the writeDecisionPersistedState still accepts a boost:optional<Timestamp> when there must not be a case in which we don't have an actual timestamp.

      Attachments

        Activity

          People

            tommaso.tocci@mongodb.com Tommaso Tocci
            tommaso.tocci@mongodb.com Tommaso Tocci
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: