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

XMLWordPrintableJSON

    • Type: Improvement
    • Resolution: Duplicate
    • Priority: Major - P3
    • None
    • Affects Version/s: None
    • Component/s: None
    • None
    • None
    • 3
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      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.

              Assignee:
              Stennie Steneker (Inactive)
              Reporter:
              David Wagner
              Votes:
              1 Vote for this issue
              Watchers:
              2 Start watching this issue

                Created:
                Updated:
                Resolved: