[SERVER-10972] correctly set timestamp in config.collections Created: 30/Sep/13  Updated: 11/Jul/16  Resolved: 30/Sep/13

Status: Closed
Project: Core Server
Component/s: None
Affects Version/s: None
Fix Version/s: 2.5.3

Type: Bug Priority: Major - P3
Reporter: Greg Studer Assignee: Randolph Tan
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Operating System: ALL
Steps To Reproduce:

Create a new sharded collection.

Participants:

 Description   

When a new collection is sharded, the config.collections.lastmod field (which here represents the sharding time of the collection) is not correctly being written - it's always something near zero.



 Comments   
Comment by Greg Studer [ 30/Sep/13 ]

Author:

{u'username': u'renctan', u'name': u'Randolph Tan', u'email': u'randolph@10gen.com'}

Message: SERVER-8678 Implement automated config schema upgrade from v4 to v5

Correctly set timestamp in config.collections.
Branch: master
https://github.com/mongodb/mongo/commit/157e4342c22c72fa16268bf2be34617e519922be

Generated at Thu Feb 08 03:24:32 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.