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

Shard key inserted ahead of timestamp field, preventing auto-generation

    XMLWordPrintable

    Details

    • Type: Improvement
    • Status: Closed
    • Priority: Major - P3
    • Resolution: Duplicate
    • Affects Version/s: None
    • Fix Version/s: None
    • Component/s: None
    • Labels:
      None

      Description

      If a collection is sharded, and has a non-timestamp _id field, then there is no way to get a server-side timestamp to be generated in a document in that collection. This is because the server puts the _id and shard key into the first two fields of the document, and the server does not scan beyond the second field looking for uninitialized timestamps. Also see CSHARP-672, which is a different manifestation of this problem.

        Attachments

          Issue Links

            Activity

              People

              • Votes:
                1 Vote for this issue
                Watchers:
                2 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: